Database Users

Does Odin Method for CWM Recovery Work on I/O Tab?

Hi folks. I have tried the Odin process three times to try to get CWM functioning on my I/O tab with no luck.
The actual Odin process seems to work fine; however, when I reboot the tab to enter recovery mode; I never get the recovery option. I only have the USB symbol and the downloading option. Also, in the upper left corner, I have:
Fastboot USB download protocol
bootloader version unknown
baseband version %s
serial number:
lock state unlocked
What am i missing? Can the I/O tab use CWM?
Thanks!!

I had the same thing, but when I am trying to root the device it just lock on boot screen. I am not a dummy but something is wrong where several users have diffrent symptoms. I would wait until further development is done. This is still a little shaky.

Odin CWM doesn't work for some reasons ..
Use this post to get rooted
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
Follow the instructions carefully !!
Download CWM and do an Install on CWM (it will install 4.0.0.4)
copy the required files to the root directory /sdcard/ (main directory if you don't know)
-Get the roms from HERE
-Get the su_busybox_misc-sam_tab_10.1-051511 HERE
Flash in the ROM 1st .. the apply the SU update (in RECOVERYMOD BEFORE you reboot)
Data / wipe
THEN REBOOT
I missed that 2nd update zip .. and trust me its a pain to get it rooted after that ..
The same procedure will not work again once you're on TW3.1 rom .. you will need an image of the system files and NVflash now..
BTW if you can do NVflash .. then I can send you the image files for 3.1TW rooted ..

fgarcia25 said:
I had the same thing, but when I am trying to root the device it just lock on boot screen. I am not a dummy but something is wrong where several users have diffrent symptoms. I would wait until further development is done. This is still a little shaky.
Click to expand...
Click to collapse
Ha .. I have 3 IO to play with (from friends)..
1st one is rooted out of the box ..
2nd one cannot communicate on FASTBOOT
3rd one does everything nicely (thats the one I had the image extracted with NVFlash)

I'll say it nicely before someone comes to say it rudely, this probably belongs in a general section rather than the development section (that is, until you develop a method to get around the restriction you've found )

Workaround method
http://forum.xda-developers.com/showpost.php?p=16196597&postcount=3
Plus I have the images to go with in case you brick yours
bill.allrobots.org said:
I'll say it nicely before someone comes to say it rudely, this probably belongs in a general section rather than the development section (that is, until you develop a method to get around the restriction you've found )
Click to expand...
Click to collapse

If you have fastboot working, then rooting is as simply as 'fastboot boot [cwm recovery filename].img'
I spent a long time getting fastboot to work, but the only fix was to finally download PDANET software to my PC and install it while it was connected to my tab. After that I got fastboot working.
Fastboot made the rooting process 100% easier. You can root any stock ROM with it and not have to reflash to 3.0.1.

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

I had the same problem with my I/O. I finally got a recovery option. What I did was flash the Euro version of TW located in the development section (which is buggy as ****).. After that I Installed CWM and flashed pershoot's root tools. Then I flashed the latest TW Rom. Everything is running smoothly, despite the samsung apps fc. Be weary of the disclaimers located on all the sections I have suggested. All of these steps are at your own risk...

Odin worked on my I/O tab after i put TW on it. I had to boot the tab into CWM via fastboot from a mac

Noobs guide to root MZ604 GED 4.1.2

Ok so I am in the process of doing this myself. I'm kind of doing this off my own back as I cannot get the AIO tools etc. to work, but there is a nice way of gaining root on 4.1.2. This is on a UK bought Xoom, but it is a MZ604 that has been added to the Google Experience Device program.
Disclaimer: This should be obvious by now in these threads, but I, nor anyone else who's work is involved in this are NOT responsible for anything that happens to your Xoom. By following this guide you are accepting this as fact. All that being said, good luck!
So, assuming you have an unlocked bootloader and with your xoom connected to a PC running Windows do the following:
1) Download the root zip attached (thanks to matt4321 for sharing solarnz zip in the original thread: http://forum.xda-developers.com/showthread.php?t=1965330 )
2) Download the latest version with install scripts from here and extract the windows file to your desktop: http://forum.xda-developers.com/showthread.php?t=1782235 (I'm assuming you can use any recovery image with the installer, however with this at least its all in one and ready to go. I used 2.3.2.3)
3) Put the "Xoom-Universal-Root_modded_4_JB.zip" onto the external SD Card (MAKE SURE IT IS A .ZIP, do NOT extract)
4) Run the RUNME file inside the windows folder on your desktop
5) Use option 2 to boot into fastboot
6) Once fastboot is loaded use option 1 in the prompt
7) This will then install the recovery.
8) Power + volume up to reboot
9) Do not let the device boot into android, it will get rid of the new recovery menu, hold power (on the Motorola dual core splash) and get the device to turn off before android starts loading.
10) Once the Xoom is off, start it again, pressing the volume down key rapidly until you see some options at the top, select recovery, press volume up.
11) Welcome to your new recovery! So, we need to install the root update. So select install zip.
12) Choose the root zip, go through the options and install it.
13) Reboot your device
14) Check for SuperSU
Congratulations, you should now have root on your 4.1.2 GED'ed Xoom MZ604.
Hope this helps someone, as I've been stuck doing this for a few hours now and just figured it out by reading countless threads about this.

Worked for me after I sorted out the Motorola drivers on my PC so that the adb driver worked properly.
Good work
Sent from my Xoom using Tapatalk 2

How do i know what the model number is? I just checked and it just said xoom this is the few threads i saw where they said it worked
Sent from my T1 using xda app-developers app

us mz604
Will this work on a us mz604

If you plan to flash custom rom there is no need to root your xoom
Just unlock bootloader
Flash cwm or twrp
Flash your favorite rom
Tada you will have awesome rooted xoom

Thank you, that is a nice and easy guide.

nevermind, found it.

Update fails - want to flash custom rom - need some advice

Now here's the situation:
I'm still on an older ROM version (4.2.1 - see attachment)
A while ago my tablet told me there was an update. I wanted to get it, it downloads but it always fail to apply the update.
What I've done to the device so far is that I've used motochopper to root the device and got rid of some ASUS apps.
So since it refuses to update, I've decided to unlock it, flash a custom recovery and get myself a custom rom.
But I've read a lot about people bricking their devices and I doubt it'll be as easy as it was on Nexus 4 and Nexus 7 - so I need some advice on how exactly to do it.
Recently I found the thread that enables us some sort of nvflash although being on JellyBean. They were talking about a specific version of bootloader and I'm not certain if I have this bootloader since I'm on an older JellyBean version. Of course I would like to use this bricksafe as well - just in case
Can someone lead me to a guide or instruct me how to do it? I don't want to brick this device
Thx in advance

l33ch0r said:
Now here's the situation:
I'm still on an older ROM version (4.2.1 - see attachment)
A while ago my tablet told me there was an update. I wanted to get it, it downloads but it always fail to apply the update.
What I've done to the device so far is that I've used motochopper to root the device and got rid of some ASUS apps.
So since it refuses to update, I've decided to unlock it, flash a custom recovery and get myself a custom rom.
But I've read a lot about people bricking their devices and I doubt it'll be as easy as it was on Nexus 4 and Nexus 7 - so I need some advice on how exactly to do it.
Recently I found the thread that enables us some sort of nvflash although being on JellyBean. They were talking about a specific version of bootloader and I'm not certain if I have this bootloader since I'm on an older JellyBean version. Of course I would like to use this bricksafe as well - just in case
Can someone lead me to a guide or instruct me how to do it? I don't want to brick this device
Thx in advance
Click to expand...
Click to collapse
This THREAD has all the info you need to do NVFlash. It's based on 10.6.1.15 something bootloader which I believe is the same as the latest Asus official. If you're on 4.2 rom, you can flash the flatline img. and generate the necessary files from there. Once that done, you can use either the provided CWM or the latest 4.2 TWRP to flash any compatible custom rom (4.3). Have fun.

graphdarnell said:
This THREAD has all the info you need to do NVFlash. It's based on 10.6.1.15 something bootloader which I believe is the same as the latest Asus official. If you're on 4.2 rom, you can flash the flatline img. and generate the necessary files from there. Once that done, you can use either the provided CWM or the latest 4.2 TWRP to flash any compatible custom rom (4.3). Have fun.
Click to expand...
Click to collapse
First of: thanks for your reply
Guide says something about bootloader 10.6.1.15.3 - I still have an even older one (10.6.1.8...) - will it still work?

l33ch0r said:
First of: thanks for your reply
Guide says something about bootloader 10.6.1.15.3 - I still have an even older one (10.6.1.8...) - will it still work?
Click to expand...
Click to collapse
Yes, that version will work because it is on the 4.2 bootloader.
Sent from my TF300T using xda app-developers app

Only works on unlocked device?
Ok I'll try like this
These are the steps I would do: (I pray someone to look over these steps and correct me if I'm wrong )
1.) Go to asus site and download unlock_v8 and run it so to unlock my tablet.
2.) I go to androidroot.mobi and download flatline_tf300.img and nvflash-tools-win32.zip (win32? Hope that does not stand for 32-bit and hope it will work on 64-bit)
3.) I reboot my device into Fastboot (don't know exactly what that means "Please note that for transformer tablets the fastboot command might require the option "-i 0x0b05"" - at this stage the device is already connected to the pc and just in case it's not in fastboot I should run this command?)
4.) I use cmd.exe to type in these commands. In which directory? In the directory where I unzip the files from nvflash-tools-win32.zip? The guide is not too specific on that.
5.) I type in "$ fastboot flash recovery flatline_device.img" (I know for device I use tf300) which will flash the recovery.
6.) I reboot my device (let android boot?) and reboot again into recovery. (power + vol down?)
7.) I select "Advanced - Wheelie" and Step 1: Flash AndroidRoot BL and find myself with a custom bootloader.
8.) It says the device will power off. Automatically? However, I boot into android and after that reboot again into recovery mode.
9.) I choose Step 2 which will generate wheelie blobs
10.) I follow the on screen prompt to retrieve my blobs (anyone has a screenshot of that? Or is it self-expalantory?)
All this time the device is connected to pc via usb?
11.) Now I reboot my tablet into APX mode - after Step 10: am I still in recovery or booted to Android?
12.) If my tablet is recognized I type "$ wheelie --blob blob.bin" into cmd
13.) Then I will type in the commands to obtain the backups
Still got a few questions though. The device is connected to PC throughout this whole procedure, right? Where to start cmd (do I have to put the files from nvflash-tools into a specific folder from where I start cmd.exe?)
And after this procedure is done do I need to flash anything else? Or will I be then equipped with a working recovery that allows me to flash custom roms?
Thanks in advance for anyone who's taking time to answer my maybe uninformed questions but I'm kind of having troubles following the guide

Flashing Cyanogenmod Rom Error

Device: Nexus 7 (Wi-Fi) (Old one)
Android: 4.3
When i go to flash cyanogenmod 10.2.0-grouper.zip i get this error
Updating partition details...
Installing 'usb-otg/cm-10.2.0-grouper.zip'...
Checking for MD5 file...
Skipping MD5 Check: no MD5 file found.
assert failed: getprop("ro.product.device") == "grouper" | | getprop("ro.build.pr
E:Error executing updater binary in zip '/usb-otg/cm-10.2.0-grouper.zip'
Error flashing zip 'usb-otg/cm-10.2.0-grouper.zip'
Updating partition details...
Can anyone please help this has been going on forever now and its getting super annoying.

What recovery are you using? Last I heard TWRP over 2.6.3.0 had issues. Try that certain version or use CWM
Sent from my Nexus 5

Pirateghost said:
What recovery are you using? Last I heard TWRP over 2.6.3.0 had issues. Try that certain version or use CWM
Sent from my Nexus 5
Click to expand...
Click to collapse
Lol ok ill try that. I'm on 2.6.3.1 ill try the other version of TWRP first.

How Did You Solve This?
HVC FOG3Y34 said:
Lol ok ill try that. I'm on 2.6.3.1 ill try the other version of TWRP first.
Click to expand...
Click to collapse
So can you give me a little more detail on what you did? This is my first unlock, root, custom recovery, and custom ROM ever, so if I made a mistake, I'm not sure I could even identify it. I used wugfresh's Nexus Root Toolkit to reach this point.
I have TWRP 2.6.3.1. Is the solution to flash a previous version of TWRP? If so, can you direct me to instructions for that?

StarSphere said:
So can you give me a little more detail on what you did? This is my first unlock, root, custom recovery, and custom ROM ever, so if I made a mistake, I'm not sure I could even identify it. I used wugfresh's Nexus Root Toolkit to reach this point.
I have TWRP 2.6.3.1. Is the solution to flash a previous version of TWRP? If so, can you direct me to instructions for that?
Click to expand...
Click to collapse
Hey im sorry. i don't really remember what i did, it was a very annoying time for me. All i remember is googling most of the stuff. Just google how to flash custom recovery on nexus 7 jelly bean or something. sorry...

StarSphere said:
So can you give me a little more detail on what you did? This is my first unlock, root, custom recovery, and custom ROM ever, so if I made a mistake, I'm not sure I could even identify it. I used wugfresh's Nexus Root Toolkit to reach this point.
I have TWRP 2.6.3.1. Is the solution to flash a previous version of TWRP? If so, can you direct me to instructions for that?
Click to expand...
Click to collapse
Fastboot flash recovery nameofrecoveryimage.img
It's that simple
Sent from my Nexus 5

Complete Instructions
I'm a newbie, and this is what I did. I can't take responsibility for anything that happens to anyone's device, nor answer any questions, because I only half understand it myself. I am sorry I can't include links. I am too new, and the website won't trust me to do that. So, you will have to search for these things on your own.
Download Stuff to your PC Note: Some antivirus software may trigger false positives on these kinds of files and block them from downloading, so you may have to temporarily disable the website shielding portion of your program.
1) The fastboot.exe file. If you want a big download, you can get it in the Android SDK. However, I got it from the CyanogenMod Installer. The installer failed to work with my device, but conveniently downloaded the fastboot.exe file for me. I'm not sure I would recommend this route if you don't want CyanogenMod.
2) TWRP 2.6.3.0. You can get it from androidfilehost.
Safety Stuff
1) Compare the MD5 code on the website to the one in your downloaded TWRP image.
A Windows utility to do that is called MD5 SHA Checksum Utility.
An Android utility to do that is called MD5 Checker.
2) Completely back up your current Android ROM. Nexus Root Toolkit is great for this and many other things. It can be downloaded from wugfresh.
The Custom Recovery Flash
1) Make sure USB debugging is still enabled on your Android device. The video links on wugfresh's page can show you how to do that.
2) Make sure your Android device is connected to your PC via USB cable.
3) Boot your Android device into the bootloader. I used Nexus Root Toolkit -> Advanced Utilities Launch -> Reboot Bootloader to do this, but I think you can also do it by turning your device off, then holding down the Power and Volume Down buttons simultaneously (don't quote me on that).
2) Search for the location of fastboot.exe on your PC. Mine was in my user directory, where CyanogenMod's installer left it: C:\Users\{Username}\cminstaller\bundle\win32
3) On your PC, open a command line. Go into the directory where you found fastboot.exe above.
4) Type fastboot flash recovery {Complete directory location and file name of TWRP image}. If you would rather not be using the complete directory location, you can always copy the TWRP image into the same directory as the fastboot.exe file, before doing this step.
5) The command window should soon say "finished". Mine took under 2 seconds.
6) On your Android device, the bootloader should currently have a big green arrow that says "Start". Press the volume down button until the arrow says "Recovery". Then press the power button. Your device should now start TWRP 2.6.3.0.
Best of all, using TWRP 2.6.3.0 for custom recovery, instead of the newest version, really did solve the original problem. Yeah!
Unfortunately, the next time I used Nexus Root Toolkit, it insisted on updating back to TWRP 2.6.3.1. So, hopefully I won't have to flash another ROM in the near future and the next TWRP version will fix the problem more permanently.

Root, recovery and custom rom setup for Galaxy S5 (SM-G900I)

Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
I'm currently running Stock Android, Marshmallow version 6.0.1 with the 1 November 2016 Security Patch.
The model of my phone SM-G900I (Australian edition).
So I've come across the following links with the instructions on how to root and install recovery, though quite confusing.
http://forum.xda-developers.com/show....php?t=2699648
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
If neither of the above methods work I have seen mentions of "flashing root" via TWRP.
Are there any known instructions on how to do that on XDA or any other website?
Or is it just a matter of obtaining the superSU zip file from https://download.chainfire.eu/696/supersu/ and flashing it?
The other information seems straight forward re using the Samsung Tool to backing up the device and the EFS .
Any help would be much appreciated.
Thank you.

just flash the .img file in download mode, and dont use the asc file at all. also dont use twrp 3.0.2-2, just use 3.0.2 (not 3.0.2-1 or 3.0.2-2 as they can be pretty buggy). Towelroot has long since become irrelevant back in the 5.0 days unfortunately so all you need to do is find the appropriate supersu.zip file and put it on your phones sd card (either internal or external), boot into recovery an install that zip via TWRP then reboot. Should be good to go. The classic "root via recovery" method

Paul_Lunardi said:
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
.
.
Click to expand...
Click to collapse
1. Plug in your phone and let the drivers load.
If phone unrecognized then head to Playstore you can find loads of apps for drivers
2.unplug your phone and turn it off
3.Load odin.
Some versions of Odin are outdated. So watch for that.
4.Holding your turned off phone. Hold the volume down power and home buttons. Done correctly it should bring you to a page saying custom Roms can damage your blah blah. Volume up to continue down to reboot. Plug your phone in then Push volume up if you feel ready to Join us Oh Padawan.
Now I am sorry for the lengthy information, most likely you have already gotten to this point, but I just want to make the same page for you and future readers. No point in asking a bunch of potentially irrelevant questions when one explanation is sufficient.
5. Odin should find your phone which will be represented by a lit up colored square on the left side indicating a Com:value# which number is of little consequence just tells you which port it found it at. Do not dwell on this.
6. Using an extraction program such as .7z take your CF auto root .Tar file, not the .Asc, and extract. You should be able to find an file with ap in the extension.
7.Take the path from the URL bar of this window including the name of the ap file and copy it over to Odin. In Odin you will see the place to put it is represented by AP.
8. CLICK START AND WAIT WITH JEOPARDY MUSIC.
9. IT MAY REBOOT A FEW TIMES BUT UNTIL IT SAYS success OR FAIL IN ODIN DO NOT TOUCH.
10. Repeat steps 7-9 for twrp.img
10. Now taking this was a success turn your phone off. Unplug and holding volume UP power and home Gets you into twrp recovery. If all is well you can reboot into system. Ignore the kernel warning.

^^^^^ theres the long explanation LoL ^^^^^^^^ i disagree with step 9, but meh

Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.

Paul_Lunardi said:
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Click to expand...
Click to collapse
the cf auto root file usually isnt necessary, nor is flashing supersu really as the newer twrps have the root function built right in. Itll ask you if you want to enable superuser rights the first time you boot into it. Just swipe right and its rooted. Alternatively, flashing supersu from within twrp or the cf auto root also work. CF is the acronym for the dev ChainFire, he is the man (or she, and conversely "the woman" or whatever LOL)!! But the crux of what you need is twrp installed, from there youre usually set. Get rooted, make a nand of your stock setup and flash away. Also, id make sure to download the stock tar.md5 file of your phones firmware in case all goes awry (or to hell in a handbasket or enter clever euphemism for stuff going bad here) so you can flash the stock tarball in Odin if you get stuck in an endless bootloop and your stock restore file doesnt work. Also, when resoring from AOSP to TouchWiz or vice versa, does require a few boxes to be checked for it to work, but it happens all the time. Happy flashing and feel free to ask away if you run into anything man!

Thanks all for clarifying.
I did have some difficulties along the way though I did successfully install twrp.
So I downloaded one of the latest versions of odin on mums computer. Laiche the twrp tar file in the ap section. Loaded it then restarted the device. Ran recovery though it was still the default android recovery ie it appeared as though nothing had changed. I looked at another forum which suggested to turn ooff the auto reboot option in odin and perform a battery pull and then launch directly into twrp. This actually worked after much agony.
I then loaded a superuser zip and flashed it onto the phone.
Rebooted confirmed that the phone was rooted.
I then relaunched the twrp recovery and ran a nand? backup of my device. Then I attempted to install a custom rom ie resurrection remix. Unfortunately it did load though the screen appeared to freeze after boot and was therefore unusable. Thank goodness the restoring of the backup worked.
I'll reattempt the installation of a custom rom very soon. Fingers crossed.
Thanks.