I've been struggling installing custom roms on my phone so I figured I'd document the process to help out anyone else starting out. I'd like to thank everyone for helping me figure this out and for the hard work of the community for making this possible.
Edit: My goal was to come up with a way to install CM9 while leaving the original system it came with and all my settings and apps. I understand how to do TitaniumBackup and how to save specific apps/files to but I wanted an exact backup of my original system alongside any custom rom so I just wrote down the steps I used to make it happen.
Root the system
1.First apply one click root using this tool
Further instructions here: http://forum.xda-developers.com/showthread.php?t=1319653
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
Droid 3 CWM (ClockWorkMod)
2. Install this apk onto the phone and click the first button then the second button
http://forum.xda-developers.com/attachment.php?attachmentid=882933&d=1328117678
3. Boot into recovery and make a backup of your system
4.Apply Fastboot package for UMTS XT860 Iusacell Mexico using RSD Lite 5.5
Further instructions here:
http://rootzwiki.com/topic/4370-sbf...959-and-56890/page__view__findpost__p__100987
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
RSD Lite: http://www.multiupload.com/T6NOEBKKLO
5. Reroot using 2.3.6 Zerg tool
Basically after flashing with RSD Lite then re-root using this tool:
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
6.Re-install CWM (Droid 3 Bootstrapper from step 2) and then apply the Bell rar file as a nandroid restore.
Further instructions here: http://forum.xda-developers.com/showpost.php?p=21446640&postcount=112
https://rapidshare.com/files/1705579381/ClockworkMod_v.5.0.2.6_Bell_2.3.6.rar
7. Reboot into the system and let the OS load again then re-install cwm (no need to reroot) and reboot back into recovery.
the trick to booting into recovery the second time is to turn the phone off, hold the m key while pressing the power button, plug in the phone to usb, choose bp tools
source: http://forum.xda-developers.com/showpost.php?p=21474818&postcount=120
restore your original backup from step 3 using advanced restore and restore the Data only and then wipe cache and dalvik cache
8. Remove CWM and install safestrap instead it involves using adb shell and removing certain files instructions found here:
http://www.droidforums.net/forum/dr...d-help-removing-clockworkmod.html#post1801072
9. Install SafeStrap once CWM is removed just install it, reboot and press the menu key while booting
http://dl.xda-developers.com/attach...5/7/9/2/5/Droid3_Safestrap_Tweaked_v1.08d.apk
10. ICS Install, at this point you have prepped your system so you can install CM9 otherwise it won't boot on the stock Bell 2.3.4
Instructions here: http://forum.xda-developers.com/showpost.php?p=22254669&postcount=61 (start at step 8 or 9 in those instructions)
-Apply CM9 Alpha 6 Zip
http://www.hash-of-codes.com/files/cm9-droid3-20120130-1730.zip
-Apply XT860 Sub-Patch (by Rick#2) for ICS Zip
http://bit.ly/Ah5b6d
Further instructions here: http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
Great tutorial
As a note, in step 6, you could flash any custom rom to /system. You might not be able to restore /data though. Can try and if no go do a data wipe. If you backup apps with titanium backup and call logs/sms/mms with mybackroot its not such a big deal. Just redownload those 2 apps and restore everything(honestly I rarely nandroid, only if im doing something im confident will end in a fastboot flash, I just use those 2 apps). Im running liberty in /systemorig and eclipse in /system
Sent from my XT860 using xda premium
Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium
Endoroid said:
Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Thanks for the tip I wouldn't have been able to get this far without your help Endoroid. I'll edit the How-To to use the same root twice, I wish mods would sticky more useful posts like zerg's root instead of pete's root and How-To such as this one.
Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?
ncho2233 said:
Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?
Click to expand...
Click to collapse
First, you may wish to just go with safestrap and try flashing g rom in safe mode. If it bootloops no harm done because your bell /system is intact
If that fails you can try using motofastboot instead of rsdlite to just flash /system. You can restore your /system with your nandroid.
As far as I know roms should work with bell 2.3.6.
If you do end up flashing the whole fastboot package with rsdlite you can make your phone appear to be bell stock. You can restore your nandroid and then mod the build.prop so about phone shows bell info. The warranty guys would have to look deep to see its been changed.
Its up to you ultimately but as I said I don't think you would have to flash the fastboot. Safestrap should work as is on bell 2.3.6. As long as you don't mess with /systemorig (nonsafe mode) its easy to remove the evidence. Uninstall safestrap recovery and remove su/superuser
If I recall correctly dasilva had his issue due to being on 2.3.4 and unable to update.
Sent from my XT860 using xda premium
Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?
ncho2233 said:
Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?
Click to expand...
Click to collapse
Correct
Safestrap was built with the idea of keeping your phone intact. You can still easily receive OTA updates and can return your phone to stock if you need to get warranty repair done
Sent from my XT860 using xda premium
dasilva333 said:
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
Click to expand...
Click to collapse
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?
白い熊 said:
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?
Click to expand...
Click to collapse
+1
1of16 said:
+1
Click to expand...
Click to collapse
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS
danifunker said:
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS
Click to expand...
Click to collapse
Thanks, and I can use it on my XT862 too?
is it possible to install the latest OTA (5.7.906), which I want to use as stock rom?
Related
I'm mobile right now... But.... The root and recovery guide are posted on rootzwiki.com... This is the LTE version... Ill pretty this up when I am gone from work....
Sent from my SCH-I510 using XDA App
poitee said:
I'm mobile right now... But.... The root and recovery guide are posted on rootzwiki.com... This is the LTE version... Ill pretty this up when I am gone from work....
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Can you make a recovery file that we can flash with Odin? A few of us have lost stock recovery snd the CWM recovery file we have available won't work.
jimh1999 said:
Can you make a recovery file that we can flash with Odin? A few of us have lost stock recovery snd the CWM recovery file we have available won't work.
Click to expand...
Click to collapse
I'm one of those few...
[HOWTO] Flash provided recovery without ODIN with broken main recovery [HOWTO]
So after 20 minutes of fiddling with things, I figured out how to get the recovery flashed without having to have recovery installed or without ODIN.
You will need
(1) Rooted LTE device
(2) ROM Manager installed *get at App market*
(3) This file from poitee's post: http://www.mediafire.com/?w45j8i0fcj0wck0
(4) ES File Explorer (or any other file explorer, I just use ES) or USB connection.
(5) Patience
=---------=-------=
Start with a rooted tab. Download the Rom manager.
1) In the ROM Manager, click on Flash ClockworkMod recovery. It will ask you what device etc, select Galaxy Tab. Wait for it to flash so it says "Current recovery: ClockworkMod 4.0.0.4".
2) After it's done, scroll down and hit All Clockwork Mod recoveries. Select 4.0.03. Let it download it and flash it.
3) Unzip the recovery.zip and take the recovery.img file and place it on the tablet.
4) Either using ES File Explorer, or just using Windows Explorer with tablet plugged in, find folder called "clockworkmod" in the SDCard root.
5) Navigate to clockworkmod/download/download.clockworkmod.com/recoveries/
There you will see some two files - recovery-clockwork-4.0.0.4-p7100.img and recovery-clockwork-4.0.0.3-p7100.img
6) Delete recovery-clockwork-4.0.0.3-p7100.img from that folder
7) Copy the recovery.img file from the ZIP above into this folder and rename it recovery-clockwork-4.0.0.3-p7100.img
8) Go back to ROM Manager, and select Flash ClockworkMod recovery, select the tab and hit OK. It will flash 4.0.0.4.
9) Place your tablet into Airplane Mode (turn off Wifi/4G/3G)
10) Scroll down again, select All Clockwork Mod Recoveries, select 4.0.0.3, and hit OK. That will now flash the recovery we just replaced.
11) Exit out of the ROM manager.
12) Push power button, hit Reboot.
13) As soon the screen goes blank, hold power button+volume rocker up till you see the box or downloading.
14) Hit UP once so the box is selected.
15) Hit DOWN once so that it boots into CWM.
*updated* Thanks jimh1999 and ~Scott~ for updates and feedback after testing this. I was a little tired and did misspell the filenames
You are done
Success....Thank You for this, I was about to give up.
Notes,
~I had to put Tab in airplane mode after step 9
~I didn't leave Tab plugged in
~nand backup will work but no progress bars in CWM
~Rom Manager will alert of recovery update, just dont update recovery
~edit per Scott's post, name of file should be recovery-clockwork to match filename structure in the folder
Finally we have recovery on LTE Tab.
THANK YOU!
My notes:
- I also had to put it into airplane mode after step 9
- I tried to flash the new recovery.img and it failed so I rebooted the tablet at this point.
- I noticed the the first recovery was named recovery-clockwork-4.0.0.4-p7100.img so I changed recovery-clockworkmod-4.0.0.3-p7100.img to recovery-clockwork-4.0.0.3-p7100.img and flashed it with no issues.
Then I booted into CWM and noticed the progress bar issue during the backup.... but.... I BOOTED INTO RECOVERY!!
Thanks again!
~Scott~ said:
THANK YOU!
My notes:
- I also had to put it into airplane mode after step 9
- I tried to flash the new recovery.img and it failed so I rebooted the tablet at this point.
- I noticed the the first recovery was named recovery-clockwork-4.0.0.4-p7100.img so I changed recovery-clockworkmod-4.0.0.3-p7100.img to recovery-clockwork-4.0.0.3-p7100.img and flashed it with no issues.
Then I booted into CWM and noticed the progress bar issue during the backup.... but.... I BOOTED INTO RECOVERY!!
Thanks again!
Click to expand...
Click to collapse
You are right about the name, same for me.
Thanks jimh1999 and ~Scott~ for updates and feedback after testing this. I was a little tired and did misspell the filenames
Updated the guide with the names and airplane steps.
tijayz said:
Thanks jimh1999 and ~Scott~ for updates and feedback after testing this. I was a little tired and did misspell the filenames
Updated the guide with the names and airplane steps.
Click to expand...
Click to collapse
Thanks to you and poitee for finding the solution. If you find any roms or kernals that work, please report back. Also can we flash the stock recovery back on this Tab?
I would still like to know why the CWM recovery would,nt work on the LTE version
First of all, let me say thanks for the effort and risk for eveyone involved. Now, please excuse my noobiness here, but is there a way in here to back up the stock rom before flashing/rooting? In other words, can I reverse this process to stock for returns/service?
I've seen how to reverse to stock the WiFi version, but this LTE is uncharted territory. Thanks!
My Galaxy LTE is bricked... Is there any way to just install the plain stock image back?
Mine was never rooted, so i'm kind of stuck, anyone have the stock recovery image?
Yep, I think what we need is the stock recovery image right? Anyone?
www.jamezelle.com/myfiles/stockrec.zip
DD the image inside to mmcblk0p2. At your own risk. Its the stock lte recovery.
Sent from my Samsung Galaxy Tab 10.1 using Tapatalk
jamezelle said:
www.jamezelle.com/myfiles/stockrec.zip
DD the image inside to mmcblk0p2. At your own risk. Its the stock lte recovery.
Sent from my Samsung Galaxy Tab 10.1 using Tapatalk
Click to expand...
Click to collapse
Can you elaborate on your instructions? I have done my fair share of ROM flashing and have used CWM for quite a while, but not sure about going back to stock on the recovery.
I accidentally used Rom Manager to flash "recovery" 4.004 to my LTE Tab and then it would no longer boot up (keeps going back to Samsung screen).
Can get to the screen to choose recovery or Odin. Then, I made it worse by flashing (with ODIN) what I thought was the correct stock image, and wound up putting the Wifi model on to it.
After quite a bit of reading (and kicking myself) ...
I have created a ODIN capable stock recovery image, and now I can get into stock recovery, but I need the rest of the LTE image to restore my unit. Can anyone make a dump of the factory stuff (other than the data) ? Heck even if I can get it working on just Wifi for now, that would be ok until the LTE image surfaces.
I really don't want to try to return it since I have only had it for 2 days and it would be pretty obvious that I had messed with it.
Thanks. I can make
Not sure if it will help but I'll wipe data and pull a nandroid if you want but I'm on cwm stock lte since I still can't figure out how tonsetup my PC for rom dev on hc
Sent from my Incredible 2 using XDA Premium App
mattj949 said:
I accidentally used Rom Manager to flash "recovery" 4.004 to my LTE Tab and then it would no longer boot up (keeps going back to Samsung screen).
Can get to the screen to choose recovery or Odin. Then, I made it worse by flashing (with ODIN) what I thought was the correct stock image, and wound up putting the Wifi model on to it.
After quite a bit of reading (and kicking myself) ...
I have created a ODIN capable stock recovery image, and now I can get into stock recovery, but I need the rest of the LTE image to restore my unit. Can anyone make a dump of the factory stuff (other than the data) ? Heck even if I can get it working on just Wifi for now, that would be ok until the LTE image surfaces.
I really don't want to try to return it since I have only had it for 2 days and it would be pretty obvious that I had messed with it.
Thanks. I can make
Click to expand...
Click to collapse
Don't worry man we'll get you going.
~Scott~ said:
Can you elaborate on your instructions? I have done my fair share of ROM flashing and have used CWM for quite a while, but not sure about going back to stock on the recovery.
Click to expand...
Click to collapse
Can you boot into android? If so I can give you the instructions to get the stock recovery back on via command line or mattj949 can post his Odin file.
I wound up returning and exchanging, but I still want to back it up in case it happens again....
However, I did make a fully working CWM ODIN flashable (for LTE Tab), however, not sure how to post it here. I left it on my office PC, will figure out how to post tomorrow.
Bricked?
Im having the same problem with rooting then using clockwork to flash recovery 4.0.0.4. Now Im stuck with the Galaxy Tab boot screen then to black then the boot screen and to black continuously.
I can access Odin but my computer doesn't recognize the Tab and never has. When I plug it in I hear the computer recognize it but gives a different sound doesn't see it. ???
Can anyone help me get this thing booted again.
Thanks
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Lyxdeslic said:
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Click to expand...
Click to collapse
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
erismaster said:
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
I think he's saying to not use rom manager at all. You can flash roms from cwm recovery.
Edit: just to clarify I mean by booting into recovery using the bootstrapper and flashing a rom from there to avoid any issues caused from the rom manager
Sent from my rooted xt860
Lyxdeslic said:
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
Click to expand...
Click to collapse
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
erismaster said:
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Lyxdeslic said:
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Click to expand...
Click to collapse
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
erismaster said:
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info man.
Ok so I have successfully rooted my phone after updating to Gingerbread. However, I had a few issues and had to read through a bunch of different posts to get there. So I'm bored and decided to consolidate everything into one.
If anyone has any other issues or fixes post them here and I will update the OP.
Credit goes to mtmichaelson and all those who helped get this working
http://androidinvasion.us/forum/index.php/topic,77.0.html
Here it is:
1. ROOT PROCESS
A. Get back to Stock:
-download the stock Zv4 ROM zip from here and put it on your external SD card- http://forum.xda-developers.com/showthread.php?t=1326893
-Back up all your apps in titanium (important: USER apps only, no data or system apps)
NOTE: It has been reported that restoring apps and data in titanium may cause some issues coming from Froyo to Gingerbread. I backed up my user apps only for easy re-install and NO data or system apps. It worked without a problem.
-MAKE SURE YOU HAVE 4G ENABLED
-boot into recovery (CWM)
-backup?
-factory reset
-select "install ZIP from SD card" in CWM, and install the stock ZIP from the link
-re-bootyour phone (you will have to re-activate it as well)
-install revo toolkit from here if it was wiped with the system reset - http://forum.xda-developers.com/showthread.php?t=1144951
-press "install recovery" and then !!!Revo Stock!!! to go back to stock recovery and wait for it to complete
B. Update to Zv6 then Zv7 (Gingerbread)
-manually search for the update and install it (this will install the v6 update)
-once that installs, manually search again to install the gingerbread update
NOTE: Some people still can't get gingerbread. Verizon has not finished rolling the update out to everyone yet.
Now here is where it gets a little dicey...
C. Rooting Your Gingerbread Phone
-pick up the rooting package from mtmichaelson here - http://forum.xda-developers.com/showthread.php?t=1326509
-follow the instructions he has on that page to obtain root
-Two issues arose for me from this point on.
2. ISSUES
A. Drivers Issue
-The first issue was that some people, including myself, couldn't download the esteem drivers.
-Some people were able to get the drivers from this page to work - http://androidnerds.net/2011/10/08/lg-esteem-oneclickroot-now-ready/.
-I was not able to get my computer to recognize my phone using the above drivers either. I would run the root command from the downloaded package and it would get stuck at "running daemon something something".
-What I did was manually uninstall the LG drivers from my computer and deleted everything "LG related"
-Then I got the drivers from the LG website at this link - http://www.lgforum.com/resources
-Scroll down to the Verizon section and download the "LG_VZW_UNITED..." drivers.
-Your phone should be recognized using the drivers from one of these links.
B. Superuser/Root access Issue - NOTE: this should be fixed now with mtmichaelson's newest root method found here - http://forum.xda-developers.com/showthread.php?t=1326509
-The second issue that came up was that the previous superuser app I had installed stayed on my phone after the updates, even though I lost root.
-The root command from the LG Esteem page would think I had root, but I actually didn't get root access.
-Apparently this issue came up on the Esteem previously and someone wrote a fix for it here - http://androidforums.com/esteem-all...-w-superuser-3-0-6-binary-3-0-3-download.html. It will uninstall the old superuser and install the new version.
3. INSTALL CWM RECOVERY
-mtmichaelson's new rooting package should automatically install CWM recovery on your phone now.
Old method:
-To get CWM back on your phone it's the same process as before the update. Get the Revo Toolkit from thecubed here and follow the instructions - http://forum.xda-developers.com/showthread.php?t=1144951
-There is sometimes an issue where the recovery does not install correctly and gives a fatal error. If this happened, make sure you have version 1.17.1 of busybox installed at system/bin. This worked for me and I got it installed correctly.
...And you should have root after trying a combination of the above. Hope this helped.
-If you have READ through this and still have any issues you can get more personalized help on the IRC channel here.
-Again I did not help with any of this, I'm just consolidating info. If you want to thank someone, thank mtmichaelson and everyone else who helped figure all this out.
-I will keep updating this as new issues arise.
Thank you for compiling this information, it is a useful reference for people to have. I know that the drivers issue took me quite a while to work out even though it is pretty simple. Hopefully this helps others to get rooted with much less trouble.
Quick question using that stock ROM will it completely unroot me?
Also a bit confused with me running revolt does that mess up me just flashing that and it has the stock boot image.
I've Revolted have you?? Sent via tapatalk plugin.
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
Hey guys, I have a new package for root for those having problems. I need testers though. If you can come on irc in about 20 minutes. It has the drivers in it also.
Sent from my VS910 4G using xda premium
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Haro912 said:
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Click to expand...
Click to collapse
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
xjli said:
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
Click to expand...
Click to collapse
Got it. I guess the first release of revo toolkit didn't have the flash stock recovery option. Can't wait to finally have gb on this thing..
Still reboots to cwm... it won't flash stock recovery. Any ideas?
xjli said:
Still reboots to cwm... it won't flash stock recovery. Any ideas?
Click to expand...
Click to collapse
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
mtmichaelson said:
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
OP updated for the new packages from mtmichaelson
xjli said:
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
Click to expand...
Click to collapse
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
jrf28 said:
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
Click to expand...
Click to collapse
Righto. Only slow 3g in my silo of an office :-/ ill let it go for a while.
Just reinstalled busybox... got it!
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
borborpa said:
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
Click to expand...
Click to collapse
It looks like it's a common problem. I haven't installed the ROM yet but mt's new gingervolt rom is supposed to make CWM stick - http://forum.xda-developers.com/showthread.php?t=1326542
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
i_t_n said:
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
Click to expand...
Click to collapse
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Haro912 said:
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Click to expand...
Click to collapse
Awesome, thank you for the quick reply. Another stupid question that i'm sure is answered somewhere on here, but what exactly will I lose when flashing a ROM, and what will I be able to restore back with a backup?
SAFESTRAP 1.09 for Droid 4 (2nd-System Bootstrap / Recovery)
[ After installation boot into recovery and make a FULL backup while in Non-Safe mode to have a full 1st and 2nd system backup for disaster recovery. ]
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. WE DO NOT HAVE A FASTBOOT FOR THE DROID 4 YET. PLEASE USE CAUTION. **
[ Make sure you get the DROID 4 VERSION ]
Download Here
Instructions for Use
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.
SPECIAL THANKS TO:
Koush who develops such a GREAT recovery system and the makes the source available for others to use.
The Atrix dev team who I pulled the internal/external SD card support from
The Defy dev team that originally developed the Bootmenu source which I stripped down and used for the Splashscreen.
As always, let me know what you think!
Reserved for future use
Literally just turned on another phone after brickin my first one....flashing now
reigndropz said:
Literally just turned on another phone after brickin my first one....flashing now
Click to expand...
Click to collapse
Please be careful! I will be posting a Droid 4 ROM created from our current MotoBlur .215 system. This can be flashed as the Safe ROM in Safestrap for those who like to "play" with their phones / settings / bloatware. That way if you mess something up you'll be able to get into Recovery and restore a backup /system.
Hashcode said:
Please be careful! I will be posting a Droid 4 ROM created from our current MotoBlur .215 system. This can be flashed as the Safe ROM in Safestrap for those who like to "play" with their phones / settings / bloatware. That way if you mess something up you'll be able to get into Recovery and restore a backup /system.
Click to expand...
Click to collapse
Will do, can't wait for that! Hey quick question....let's say I wanted to flash a zip for a mod in Safestrap. I cant flash it when SS is disabled so I have to enable it but that restores the old system. Is this where I want to toggle , install the zip and then toggle back afterwards?
reigndropz said:
Will do, can't wait for that! Hey quick question....let's say I wanted to flash a zip for a mod in Safestrap. I cant flash it when SS is disabled so I have to enable it but that restores the old system. Is this where I want to toggle , install the zip and then toggle back afterwards?
Click to expand...
Click to collapse
There's no flashing zips to the "Non-Safe" ROM in Safestrap. You can only flash zips to the Safe ROM (with Safe Mode enabled).
You only run your original ROM when Safe Mode is disabled.
Hashcode said:
There's no flashing zips to the "Non-Safe" ROM in Safestrap. You can only flash zips to the Safe ROM (with Safe Mode enabled).
You only run your original ROM when Safe Mode is disabled.
Click to expand...
Click to collapse
The problem I'm having is When Safe Mode is enabled , I cant start any ROM. I enabled Safe Mode and then restored a nandroid backup but it wont load. It hangs after the Moto boot screen. The only way it seems to work is if I disable Safe Mode which in turn loads the previous ROM, so I'm always at square one. I'm sure I am doing this wrong, just not sure what exactly it is.
Anytime i flash something in safestrap i get a bootloop. I tried atric rom and the stock rooted rom. Same results. I would log cat but usb debugging isnt enabled
Sent from my DROID4 using Tapatalk
papi92 said:
Anytime i flash something in safestrap i get a bootloop. I tried atric rom and the stock rooted rom. Same results. I would log cat but usb debugging isnt enabled
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I'll download arctic and see what's happening with it. Should be able to flash that one. But the stock rooted /system dump needs some files tweaked I think.
reigndropz said:
The problem I'm having is When Safe Mode is enabled , I cant start any ROM. I enabled Safe Mode and then restored a nandroid backup but it wont load. It hangs after the Moto boot screen. The only way it seems to work is if I disable Safe Mode which in turn loads the previous ROM, so I'm always at square one. I'm sure I am doing this wrong, just not sure what exactly it is.
Click to expand...
Click to collapse
I'm not sure restoring a nandroid backup works that way. I'll get a MotoBlur .215 for use w/ Safestrap available for download here in a bit.
papi92 said:
Anytime i flash something in safestrap i get a bootloop. I tried atric rom and the stock rooted rom. Same results. I would log cat but usb debugging isnt enabled
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Looks like someone over at rootzwiki figured something out on this. According to the post, when in the bootloop, if you go back into recovery for a second time, and boot again, supposedly it lets you into the second ROM.
Here's the official post on it:
http://rootzwiki.com/topic/19673-ics-on-droid-4/
This guy loaded ICS from the Droid Kang version of RAZR and claims it's working....I was going to give it a try in a bit, and see if it works.
garlick2 said:
Looks like someone over at rootzwiki figured something out on this. According to the post, when in the bootloop, if you go back into recovery for a second time, and boot again, supposedly it lets you into the second ROM.
Here's the official post on it:
http://rootzwiki.com/topic/19673-ics-on-droid-4/
This guy loaded ICS from the Droid Kang version of RAZR and claims it's working....I was going to give it a try in a bit, and see if it works.
Click to expand...
Click to collapse
I've loaded it as well last week and it does work but there are too many issues. Besides the one he mentioned, when you turn the screen, it gets stuck in the horizontal view and wont revert back. Also, the above method doesnt work, at least not for me. Flashing a ROM does work though without going through those steps, I am just not having luck with flashing zip's of other kinds.
Cool. Jeff8732 didn't have a lot to say about it besides the keyboard didn't light up.
I also am a bit more interested in a CM9 based ROM, my understanding that's the one that Hashcode is working on....so I'll just hang tight and wait for that.
The links here are down. Anyone have working links? Thanks.
mystik1 said:
The links here are down. Anyone have working links? Thanks.
Click to expand...
Click to collapse
http://blog.hash-of-codes.com/how-to-safestrap/
There is the link that I used.
Delete files
I was wondering if i could delete any of the safestrap backups from my SD card. It's using well over 3GB. Right now I have the following files in the backup folder:
Nonesafe:
cahce.ext3.tar
data.ext3.tar
nandroid.md5
osh.ext3.tar
system.ext3.tar
systemorig.ext3.tar
Orig:
data.ext3.tar
Safe:
data.ext3.tar
I was wondering, would it be safe to delete any of those?
Links fixed.
Two requests:
Add a shell option to the recovery menu. I really miss that feature (from AmonRa recovery on my G1).
Integrate kexec. We ought to be able to intercept the boot process and load any kernel we want, safely. On the XDAndroid builds we replace /init with a shell script that does a bunch of manipulation before exec'ing the real Android init. For a kexec boot you add a kernel argument to flag that it was kexec'd. If the shell script sees that argument, it knows kexec was already done and just passes the boot on thru. If it doesn't see the argument, it kexecs the kernel you want.
Follow this thread for more details. I also added a kexec option to our Powerdown menu (in addition to Shutdown and regular Reboot) to allow fast swapping between kernels.
http://lists.xdandroid.com/pipermail/xdandroid-dev/2011-May/000327.html
Come to think of it - can we partition the internal SD card? If so, we could create a new root partition as well. Could just use the external SD too if all else fails.
Hi to all
I wish to root my Note (GT-N7000) and am trying to follow the method described in Dr Katan's post here.
Download the [CWM zip] and put in your Ext SDCARD ] And [ SUPERSU-Busybox-Installer.zip] to SD card (internal memory)
Reboot to recovery.
Choose apply update from external storage. (use vol up/down to select, power to enter)
Choose CWM.zip and wait until CWM recovery appear.
Choose install zip from sdcard (Now use touch function to select choice)
Choose and Install SUPERSU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Click to expand...
Click to collapse
I am running the following stock ROM:-
Android Version
4.0.3
Baseband Version
N70000XXLPT
Kernel Version
3.0.15-N7000XXLQ2-CL605927
[email protected] #3
Build Number
IML74K.XXLQ2
When I hold the power button, I don't see any 'Recovery' option (The only options are 'Silent mode', 'Data network mode', 'Flight mode', 'Power off' and 'Restart'). What am I missing/doing wrong..?
Many thanks to anyone who can help.
PS. Apologies for posting this in the Q&A section. I'm relatively new so can't yet make a post in the relevant development thread.
only custom ROM users get the APM (advanced power menu)
you will have to do it manually, Power off the phone and hold volume UP + Home + Power all at once
let go when you see the GT-N7000 screen
azzledazzle said:
only custom ROM users get the APM (advanced power menu)
you will have to do it manually, Power off the phone and hold volume UP + Home + Power all at once
let go when you see the GT-N7000 screen
Click to expand...
Click to collapse
Thankyou VERY much. I did it, but haven't tried the rooting procedure yet. In the recovery menu, I saw a message about CSC being successfully applied. What does this mean...?
not sure what CSC stands for but it happens to us all, Dont worry about it, Its a good thing that it was applied successfully
Csc is country sales code. And yes as azzledazzle said, its normal to see that message.
Sent from my GT-N7000 using xda premium
I have now run into a few problems and would be very glad for some advice.
I have tried to root following the instructions below in the OP.
Download the [CWM zip] and put in your Ext SDCARD ] And [ SUPERSU-Busybox-Installer.zip] to SD card (internal memory)
Reboot to recovery.
Choose apply update from external storage. (use vol up/down to select, power to enter)
Choose CWM.zip and wait until CWM recovery appear.
Choose install zip from sdcard (Now use touch function to select choice)
Choose and Install SUPERSU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Click to expand...
Click to collapse
All went well (or so I thought) but I have 2 problems:-
I don't think I'm properly or fully rooted. After following the above steps, I installed Mobile Odin Pro (v2.45) and attempted to flash CF-Root-SGN_XX_XEU_LQ2-v5.6-CWM5.zip. I extracted the tar file, placed it on the external SD card and ran it using Mobile Odin Pro. However, upon rebooting, I see that my baseband, kernel version, build no. etc. are still showing exactly the same info in the 'About phone' section under Settings, ie.
Android Version
4.0.3
Baseband Version
N70000XXLPT
Kernel Version
3.0.15-N7000XXLQ2-CL605927
[email protected] #3
Build Number
IML74K.XXLQ2
Is this normal or have I missed an important step? I saw on another thread that perhaps I should have extracted both the tar and zimage files from the CFRoot zip, and then flashed? If so, could someone kindly tell me exactly what to do. For info, SU seems to have installed ok and has granted the necessary permissions to CWM and Mobile Odin Pro as root apps but I can't get into or use either app. What am I missing or doing wrong?
After rebooting, I can no longer use Mobile Odin Pro so cannot attempt a proper flash of whatever kernel I should be using. I can mostly now not get past the 'Loading...Checking SuperUser support...' splash screen. During this period, I see a pop-up which confirms the app has been 'granted SuperUser permissions for an interactive shell'; this pop-up usually appears several times during this loading period. Very occassionally, it gets past the Loading screen but then stays for an equally lengthy time at the next 'Loading...Detecting device model...' screen. If it gets past that, it then fails to detect any device model so I cannot use the app. What am I doing wrong? I've tried rebooting several times - no joy. I've tried uninstalling and then reinstalling the app - again, no joy.
If anyone can help me out of my rooting misery, I'd be really grateful.
One more thing - I'm not completely clear how I revert to/reinstall a stock ICS ROM once I am properly rooted or from where the phone is now? Can someone please just clarify this for me.
Apologies for the long post - just wanted to give as much information as possible.
Many thanks to all who can help
im not so sure but when you installed cwm and buzybox you did so to flash a custom rom
if you flash a custom rom you will keep the phone root and so on (supersu ecc...)
else you loose partially the root and you need to reflash the apps you lost on rebbot
so choose good cutom ics and go for it
you might try cssie xlite....180 mega
or Rocket Rom 7 700 mg
both work well
p.s. never full wipe or factory reset on ics cfroot kernell....
just do t with abyss kernel 4.2 if you need it and read about eemmmc bug crack
p.s.2 look for drkeatan posts and chasmodo....they made good walkthrough pro
lorekarf said:
im not so sure but when you installed cwm and buzybox you did so to flash a custom rom
if you flash a custom rom you will keep the phone root and so on (supersu ecc...)
else you loose partially the root and you need to reflash the apps you lost on rebbot
so choose good cutom ics and go for it
you might try cssie xlite....180 mega
or Rocket Rom 7 700 mg
both work well
p.s. never full wipe or factory reset on ics cfroot kernell....
just do t with abyss kernel 4.2 if you need it and read about eemmmc bug crack
Click to expand...
Click to collapse
Thanks for the reply. I only rooted in order to use certain root apps (Root Explorer, Titanium Backup etc) and was under the impression that the CF-Root-SGN_XX_XEU_LQ2-v5.6-CWM5.zip was basically a slightly modified stock ICS ROM with CWM included..?
largeruk said:
Thanks for the reply. I only rooted in order to use certain root apps (Root Explorer, Titanium Backup etc) and was under the impression that the CF-Root-SGN_XX_XEU_LQ2-v5.6-CWM5.zip was basically a slightly modified stock ICS ROM with CWM included..?
Click to expand...
Click to collapse
The way I've always rooted is to run the adb script on a gb from, can be found in dr K's post. You need to be rooted before you can flash cwm kernel, 2 separate processes (although combined in some scripts.
There is also a thread somewhere with pre-rooted stock roms, so you could flash one of those as normal with PC Odin and then flash cwm kernel. Might be easier.
Sent from my GT-N7000 using xda premium