Related
This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done
juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.
So has anyone followed this guide successfully yet? I don't really want to be the first...
yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?
pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App
Tnx . Very help full .
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...
I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk
**PLEASE NOTE, I AM IN NO WAY AFFILIATED WITH CWM RECOVERY. THIS THREAD IS FOR DISCUSSION/TROUBLE SHOOTING/GENERAL INFO ON CWM TOUCH AND CWM RECOVERY FOR THE SPRINT VARIANT ONLY**
Special thanks to koush, TeamEpic and everyone else involved in making CWM Recovery for our phones. Also thanks to reinbeau for allowing me to start a CWM Thread for Sprint SGSIII specifically
**WARNING: ANYONE USING TEAMEPIC'S DUALBOOT FAKE CWM RECOVERY ARE ADVISED NOT TO USE RECOVERIES IN THIS THREAD! PLEASE REFFER TO THEIR THREAD HERE**
CWM RECOVERY AND CWM TOUCH RECOVERY FOR SPRINT SGSIII (d2spr)
DOWNLOADS FOR ALL RECOVERY IMAGES CAN BE FOUND HERE
-Scroll towards the bottom for latest releases. Our device (Sprint SGSIII) is labeled as d2spr
HOW TO INSTALL?
METHOD 1
-Use adb shell or Terminal Emulator (on device)(Must be rooted)
-Download CWM Recovery and place it on the root of your internal storage and rename it to "recovery.img" (without the quotes)
-In adb shell or terminal emulator enter the following commands:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
reboot recovery
METHOD 2
-Use Mobile Odin
-Download CWM Recovery, rename it to recovery.img and place on root of internal storage
-Open Mobile Odin (may start downloading neccessary files for our device)
-Select "Open File", then select "Internal SD-Card"
-The recovery.img should be listed at the very top. Select it
-In the main menu the only Partition that should be selected is Recovery
-Scroll Down and Select Flash Firmware (after it flashes you may be automatially rebooted into recovery)
METHOD 3
-Use CWM Manager App (**ONLY NON TOUCH RECOVERY IS FREE IF YOU USE THIS METHOD)
-Download and install CWM Manager
-Open the app and select Install CWM Recovery
-Let it install. After installation completes reboot into recovery and see if it works
METHOD 4
-This is a .tar.md5 file I made for CWM TOUCH RECOVERY 6.0.1.2 (I tested it personally, it works)
-DOWNLOAD THE recovery.tar.md5 (md5 checksum: 421b6b467a304532fb19a35d960678bf)
-Open up Odin on your desktop (If using Mobile Odin, Follow same instructions as METHOD 2 except you don't rename it)
-Make sure USB Debugging IS enabled on your device and go into download mode
-once in Download Mode make sure Odin recognizes your device (should be a blue box that says COM then a number)
-In the PDA Slot navigate to wherever you saved the recovery.tar.md5 and select it (again, for the PDA Slot)
-Once selected, make sure Auto Reset and F-Reset Time are the only things checked
-Select Start
-If the installation goes right you should get a PASS! message in Odin
Latest Direct Downloads as of 8-28-12
Direct Downloads of CWM Recovery (Sprint SGSIII Only)(Latest Downloads As Of 8-28-12)
The .img's must be flashed with adb, terminal emulator, or Mobile Odin.
CWM TOUCH
recovery-clockwork-touch-6.0.1.2-d2spr.img
CWM (Regular)
recovery-clockwork-6.0.1.2-d2spr.img
BUGS:
-Incorrect time stamp on backups
-Cannot mount Internal Storage from Recovery
-Cannot create backup's using the option in ROM Manager
How to Make a recovery.tar.md5
This is a guide on how to make a .tar.md5 file to be flashed through Odin or Mobile Odin. These are good to have on hand. If you end up unrooting your phone but re root. Instead of using Odin to flash a CWM Recovery that's outdated you can make one yourself using this process, then flash it using Odin so you can boot into recovery and flash a Root from Recovery zip
I used this guide, I'll just try to expand it and make it a little more simpler for cygwin (Windows) users
1) Navigate to your cygwin directory (ex: C:\cygwin) and go to C:\YOUR_CYGWIN_DIRCECTORY\home\Owner\ and create a folder, name it to whatever you'd like (ex: recovery_odin)
2) Download your CWM recovery image and rename it to recovery.img. Place it in the folder you created in cygwin (for the rest of the guide I'll refeer to this folder as recovery_odin)
3) Double click on your cygwin.bat and type this:
Code:
cd recovery_odin
4) Enter the following commands:
Code:
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5
5) Inside your recovery_odin folder you'll find your recovery.tar.md5, flash that using Odin (PDA Slot). If you want full root acess you need to flash the Root from Recovery zip immediately after flashing your new recovery. So, in Odin prior to flashing your recovery.tar.img, make sure Auto Reboot option is not checked and you pull the battery out after your recovery successfully flashed so you can enter CWM Recovery and flash that zip (make sure the zip is on your Internal SD prior to flashing the recovery)
woOT!!! First again!
Used the adb method earlier on my own to push the CWM Touch recovery, worked as it should.
Sent from my E4GT packed full of "The Goodness" of TNz Blend ICS on Tapatalk 2 the SGS3 is charging
NICE!!!
Sent from my SPH-L710 using Tapatalk 2
I hope this will cut down on the confusion. I think every variant ha# a CWM Recovery thread in their respective dev sections. I'm leaving right now but when I get back I'll finish the rest of the posts
Sent from my SPH-L710 using xda premium
I suppose this will suffice, till I get my TWRP fix. <3 Thank you.
I used the mobile Odin method earlier today. Worked great!
Sent from my Samsung Galaxy SIII using Tapatalk
I used method 5, I love Rom Manager.
But when backing up rom from rom manager,
it goes to recovery and starts and quickly aborts with error.
It will not do a nandroid, I tried many times.
But if I do a backup directly from recovery clockwork it works
fine other than names with the year 1970. Why doesn't Rom Manager
work, and I have latest version and installed sprint GS3 right from it.
Nice conflation of goodies on this thread
CM9'rs running off Epic CM Team's temp kexec 'dual-boot / red Fake CWM' have been advised NOT to use ROM Manager (ie, to obtain CWM Touch or Nightly updates etc.)......... could bode badly.
sonarchist said:
Nice conflation of goodies on this thread
CM9'rs running off Epic CM Team's temp kexec 'dual-boot / red Fake CWM' have been advised NOT to use ROM Manager (ie, to obtain CWM Touch or Nightly updates etc.)......... could bode badly.
Click to expand...
Click to collapse
Thank you I will post a warning when I'm home
Sent from my SPH-L710 using xda premium
Where are the cm9 nightlies for sprint. I see no thread about it here in the Dec forum?
Sent from my SPH-L710 using Tapatalk 2
ladle3000 said:
Where are the cm9 nightlies for sprint. I see no thread about it here in the Dec forum?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
You can find those here
fergie716 said:
You can find those here
Click to expand...
Click to collapse
How'd you find these. They don't show in the dev forum for me
Sent from my SPH-L710 using Tapatalk 2
ladle3000 said:
How'd you find these. They don't show in the dev forum for me
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I'm assuming your on Tapatalk, go to all Forums, Scroll to the very bottom and look for the SGSIII threads, then Sprint Original Development
So if I am already rooted and have the non touch cwm recovery installed I can just not into recovery and flash the touch version?
Sent from my SPH-L710 using Tapatalk 2
JuggZaPoppiN said:
So if I am already rooted and have the non touch cwm recovery installed I can just not into recovery and flash the touch version?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
yea grab the zip file in the second post and flash it. I've read some ppl having issues with it not sticking after a reboot so I would recommend either using adb or mobile odin, both of those have worked for me. I personally haven't used the zip's CWM published
In fact I removed the links to the CWM zips. I haven't tested those so I can't vouch for them
Use the CWM Images (direct Links in post#2), or use the .tar.md5 file I provided in Method 4 and use those.
fergie716 said:
In fact I removed the links to the CWM zips. I haven't tested those so I can't vouch for them
Use the CWM Images (direct Links in post#2), or use the .tar.md5 file I provided in Method 4 and use those.
Click to expand...
Click to collapse
The zips "work" but they do not "stick"....the IMG file does make recovery stick though...just my 2 cents...
If I'm creating a duplicate post, I apologize. However, I am trying to find a zip of CWM Touch 6.0.2.3.
As I am creating this post, I see that there may be a recovery in other forums. Is the recovery the same across all devices? I just want to make sure I get the right one for my S3.
Thank you,
The one and only GBP.
Just made these .zips...
CWM 6.0.2.3 (SGS3 T-Mobile)
CWM 6.0.2.3 Touch (SGS3 T-Mobile)
Flash either of them in Recovery Mode.
CWM SITE
Thank you, I really appreciate your help.
So I know how to do that the next time, how did you create the zip file? When I was at the CWM site, all I could download was an IMG file.
Try using twrp its nice and user friendly if you want an alternative touch based recovery just download goo manager from the play store and give it a try can't hurt
Sent from my SGH-T999 using xda premium
HOW to create a .zip (flashable rom when new version comes out)
1. Started with older CWM .zip ROM that I knew worked in past...
2. Download Newest CWM Recovery .img file from CWM SITE...
3. Extract older CWM .zip and rename to newest Version number... example "Recovery_CWM_v6.0.2.3"
4. rename newest CWM recovery .img to "recovery.img" and copy to your extracted folder. (Write over older version)
5. Re-compress with WinRAR or 7-Zip and make sure it's .ZIP format, not .RAR or another type.
6. All done
*** All your doing is taking recovery image and updateing into newly created .zip
*** in flash mode, the Recovery option to INSTALL (or flash any zip) always reads META-INF\com\google\android\"updater-script"
the script it reads for this example is...
ui_print("Please Wait");
ui_print("Flashing recovery");
show_progress(0.200000, 10);
package_extract_file("recovery.img", "/dev/block/mmcblk0p18");
show_progress(0.100000, 0);
ui_print("Success!!!");
so you can see it 's just gonna put "recovery.img" in your "mmcblk0p18" Partition which we can see is the recovery partition.
there are many partitions like System, Data, Flexrom, Cache, Dvalk Cache, SD Card, etc...they all have same start with different ending numbers mmcblk0p18
I agree with dscott973, that TWRP v2.3.3.1 is the best RECOVERY ! I'd change to that one (my opinion)
You can do the same thing by puting TWRP image renamed to "recovery.img" in the same format as this thread example (and rename folder accordingly),
but very important, always make sure your using the same type. Make sure your using for Samsung Galaxy S3 (TMobile type).
Example : Don't mix Verizon or AT&T type (just know what your doing and label it correctly)
ktmdave7 said:
1. Started with older CWM .zip ROM that I knew worked in past...
2. Download Newest CWM Recovery .img file from
3. Extract older CWM .zip and rename to newest Version number... example "Recovery_CWM_v6.0.2.3"
4. rename newest CWM recovery .img to "recovery.img" and copy to your extracted folder. (Write over older version)
5. Re-compress with WinRAR or 7-Zip and make sure it's .ZIP format, not .RAR or another type.
6. All done
*** All your doing is taking recovery image and updateing into newly created .zip
*** in flash mode, the Recovery option to INSTALL (or flash any zip) always reads META-INF\com\google\android\"updater-script"
the script it reads for this example is...
ui_print("Please Wait");
ui_print("Flashing recovery");
show_progress(0.200000, 10);
package_extract_file("recovery.img", "/dev/block/mmcblk0p18");
show_progress(0.100000, 0);
ui_print("Success!!!");
so you can see it 's just gonna put "recovery.img" in your "mmcblk0p18" Partition which we can see is the recovery partition.
there are many partitions like System, Data, Flexrom, Cache, Dvalk Cache, SD Card, etc...they all have same start with different ending numbers mmcblk0p18
I agree with dscott973, that TWRP v2.3.3.1 is the best RECOVERY ! I'd change to that one (my opinion)
You can do the same thing by puting TWRP image renamed to "recovery.img" in the same format as this thread example (and rename folder accordingly),
but very important, always make sure your using the same type. Make sure your using for Samsung Galaxy S3 (TMobile type).
Example : Don't mix Verizon or AT&T type (just know what your doing and label it correctly)
Click to expand...
Click to collapse
Thank you for your help. I'll take a look at TWRP. I just wanted the latest recovery because I'm considering upgrading to 4.2.1. I've read that the older recoveries struggle with the new file system, due to multiple users.
Merry Christmas
GBP85 said:
Thank you for your help. I'll take a look at TWRP. I just wanted the latest recovery because I'm considering upgrading to 4.2.1. I've read that the older recoveries struggle with the new file system, due to multiple users.
Merry Christmas
Click to expand...
Click to collapse
^So true, found that out the hard way... :silly:
ok. new noob here. so i have downloaded the file to root and install cwm on my gs3 from rootgalaxys3.com. the cwm in it won't allow me to flash a new rom. 'assert failed' is the only thing that keeps showing up. i looked into it and i think i have to upgrade my cwm version. so i found this link to the touch version for the galaxy s3. after i download it and i go to throw it in to the PDA slot in odin. its not there. so i extract it and i find 'meta-inf' file and a "recover.img" i can end up putting that in to the pda slot. BUT it ends in .img... is this ok or does the file have to end in .tar to flash properly and work?
PLEASE HELP ME!!!!
justinjrdawson said:
ok. new noob here. so i have downloaded the file to root and install cwm on my gs3 from rootgalaxys3.com. the cwm in it won't allow me to flash a new rom. 'assert failed' is the only thing that keeps showing up. i looked into it and i think i have to upgrade my cwm version. so i found this link to the touch version for the galaxy s3. after i download it and i go to throw it in to the PDA slot in odin. its not there. so i extract it and i find 'meta-inf' file and a "recover.img" i can end up putting that in to the pda slot. BUT it ends in .img... is this ok or does the file have to end in .tar to flash properly and work?
PLEASE HELP ME!!!!
Click to expand...
Click to collapse
Download ROM manager for cwm or goo manager for twrp and flash recovery from app in goo manager hit the menu button and flash recovery script. I dont know how to do it off hand in ROM manager but it is in there
Sent from my SGH-T999 using xda premium
The 2 files I posted earlier here are for FLASHING in RECOVERY only, not made for ODIN install.
another separate way to install Recovery is...
A) Download app from Market called "Terminal Emulator" (it's like using ADB commands on cell phone instead of PC).
B) use the same "recovery.img" from either of my 2 Zips earlier posted and then copied it to External SDCard (name of .img file has to match same name as in text below)
C) Run Terminal Emulator and enter these 2 command lines (Cell has to be ROOTED for su permissions to work)
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
D) Check to make sure you have Recovery.
-with cell being off, Use {Volume Down, Home, Power} to load up recovery and check it.
To directly answer the question, you can only flash .tar files with Odin.
ktmdave7 said:
CWM 6.0.2.3 (SGS3 T-Mobile)
CWM 6.0.2.3 Touch (SGS3 T-Mobile)
Flash either of them in Recovery Mode.
CWM SITE
Click to expand...
Click to collapse
Seriuosly... just attach things like this.. They are small enough. Especially since you chose to use a stupid file hosting site that tells you to register for a free account but doesnt even give that option.
ktmdave7 said:
CWM 6.0.2.3 (SGS3 T-Mobile)
CWM 6.0.2.3 Touch (SGS3 T-Mobile)
Flash either of them in Recovery Mode.
CWM SITE
Click to expand...
Click to collapse
/
Useless, i cant even create a free basic account, could you unload it somewhere else please?
Here you go: http://db.tt/okfh9vzU
ktmdave7 said:
The 2 files I posted earlier here are for FLASHING in RECOVERY only, not made for ODIN install.
another separate way to install Recovery is...
A) Download app from Market called "Terminal Emulator" (it's like using ADB commands on cell phone instead of PC).
B) use the same "recovery.img" from either of my 2 Zips earlier posted and then copied it to External SDCard (name of .img file has to match same name as in text below)
C) Run Terminal Emulator and enter these 2 command lines (Cell has to be ROOTED for su permissions to work)
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
D) Check to make sure you have Recovery.
-with cell being off, Use {Volume Down, Home, Power} to load up recovery and check it.
Click to expand...
Click to collapse
Don't you mean Volume Up, Home, Power for Recovery?
Can someone reload these links? I need them badly thanks
i have a old version of cwm i want 2 update cwm .. can some one make a step by step?
iam not a total noob but i dont wanne brick my note 2 haha..
iam now on miui
DLK7
Use mobile odin to flash cwm img file.
Download it and rename it to recovery.img
I recommend using twrp.
Sent From Samsung's Galaxy Note II Using Internet
UtkarshGupta said:
Use mobile odin to flash cwm img file.
Download it and rename it to recovery.img
I recommend using twrp.
Sent From Samsung's Galaxy Note II Using Internet
Click to expand...
Click to collapse
so i download the odin app... then i must download the tar file?
and then done?
thx anyway ^^ the app looks great
download recovery from here[url]
download the one that says " Samsung Galaxy Note 2 (HSPA+) "
what you are gonna get is an *.img file whatever it's name is.
rename it to recovery.img
push it to your phone preferably to the root of internal sd card
open mobile odin
tap recovery
select internal sd card
locate your file.
now odin should say something like - " /sdcard/recovery.img " or wherever your file was located.
don't touch anything else
just scroll down and hit the flash firmware button.
and in 3..2..1.. your phone will BBBLLLAAASSSTTT
into recovery
imao use twrp - [URL="http://goo.im/devs/OpenRecovery/n7100"]download from here
scroll down and download the one in img format and follow the same steps.
current version as of time of posting this
cwm - 6.0.1.9
twrp - 2.3.3.1
only use the latest version
UtkarshGupta said:
download recovery from here[url]
download the one that says " Samsung Galaxy Note 2 (HSPA+) "
what you are gonna get is an *.img file whatever it's name is.
rename it to recovery.img
push it to your phone preferably to the root of internal sd card
open mobile odin
tap recovery
select internal sd card
locate your file.
now odin should say something like - " /sdcard/recovery.img " or wherever your file was located.
don't touch anything else
just scroll down and hit the flash firmware button.
and in 3..2..1.. your phone will BBBLLLAAASSSTTT
into recovery
imao use twrp - [URL="http://goo.im/devs/OpenRecovery/n7100"]download from here
scroll down and download the one in img format and follow the same steps.
current version as of time of posting this
cwm - 6.0.1.9
twrp - 2.3.3.1
only use the latest version
Click to expand...
Click to collapse
woooww many thanks !!! when iam home i gonne try it
edit:
it wooorrkks greaat
Not sure if this has been posted already but, this exact process for rooting works for almost ANY android device the program is very easy to use and I will do my best to try and explain how it works.
First, download this ROOTING TOOL
BLU Tank 4.5 Recovery Provided by lopestom: DOWNLOAD
SuperUser: DOWNLOAD
MobileUncle Tools: DOWNLOAD
Now that you have all of these files I will teach you step by step to achieve root + CWM.
ROOTING:
1. Extract the rooting tool to your computer the folder should be called "VROOT" now open the file Root.exe and this image will appear. (MAKE SURE YOUR PHONE IS CONNECTED VIA USB WITH INSTALLED DRIVERS)
2. CLICK ROOT.
The program will install a chinese version of superuser which we will delete after CWM installation. (YOUR PHONE WILL REBOOT, THIS IS NORMAL)
3. After reboot, you may now exit the program.
CWM:
1. Now that we are rooted, we can install CWM. While your phone is still plugged into your computer place the MobileUncleTools.apk into your phones storage.
2. Exract the recovery "BLU Tank 4.5.zip" to your computer and put the recovery image file into your phone.
3. Go to your phone and load the application "File Manager" and install the program MobileUncletools.apk that you just put on your phone.
4. Run the program Mobile Uncle Tools on your phone:
Next:
5. Once you Select the recovery.img your phone will prompt you to flash the recovery, click YES, it will then prompt you to reboot your phone into recovery then choose YES.
6. You should now be in CWM.
NOW TO REMOVE CHINESE SUPERUSER.
1. Choose to install a zip from SD CARD > Choose UPDATE-SuperSU-v1.41.zip > Install
2. CWM will remove chinese SU and you now have Chainfire SU.
Done.
swindillon said:
Not sure if this has been posted already but, this exact process for rooting works for almost ANY android device the program is very easy to use and I will do my best to try and explain how it works.
First, download this ROOTING TOOL
BLU Tank 4.5 Recovery Provided by lopestom: DOWNLOAD
SuperUser: DOWNLOAD
MobileUncle Tools: DOWNLOAD
Now that you have all of these files I will teach you step by step to achieve root + CWM.
ROOTING:
1. Extract the rooting tool to your computer the folder should be called "VROOT" now open the file Root.exe and this image will appear. (MAKE SURE YOUR PHONE IS CONNECTED VIA USB WITH INSTALLED DRIVERS)
2. CLICK ROOT.
The program will install a chinese version of superuser which we will delete after CWM installation. (YOUR PHONE WILL REBOOT, THIS IS NORMAL)
3. After reboot, you may now exit the program.
CWM:
1. Now that we are rooted, we can install CWM. While your phone is still plugged into your computer place the MobileUncleTools.apk into your phones storage.
2. Exract the recovery "BLU Tank 4.5.zip" to your computer and put the recovery image file into your phone.
3. Go to your phone and load the application "File Manager" and install the program MobileUncletools.apk that you just put on your phone.
4. Run the program Mobile Uncle Tools on your phone:
Next:
5. Once you Select the recovery.img your phone will prompt you to flash the recovery, click YES, it will then prompt you to reboot your phone into recovery then choose YES.
6. You should now be in CWM.
NOW TO REMOVE CHINESE SUPERUSER.
1. Choose to install a zip from SD CARD > Choose UPDATE-SuperSU-v1.41.zip > Install
2. CWM will remove chinese SU and you now have Chainfire SU.
Done.
Click to expand...
Click to collapse
I tried with no luck. Phone is already rooted with the same method you mentioned. I flash the recovery image using the app, and the phone reboots to the stock recovery mode.
I'm not running the phone on a stock firmware.. Could that be the problem?
Manar Aleryani said:
I tried with no luck. Phone is already rooted with the same method you mentioned. I flash the recovery image using the app, and the phone reboots to the stock recovery mode.
I'm not running the phone on a stock firmware.. Could that be the problem?
Click to expand...
Click to collapse
I have the SAME problem! SU ok but the phone reboots to the stock recovery.... My firmware is original... What I do now?
Sorry, but VROOT threads are being closed by the moderation team because they appear to be collecting information off of devices. So, until this method is verified to be working safely and without malware, I would advise everyone not to use this method. Please report them to the moderation team.
Thanks!