Related
I've poked around the forum looking for solutions but found no situation the same as mine. I'm beginning to prepare to flash a new ROM onto my Eris, so I was doing to do a nandroid backup. I have a rooted 2.1 (non-OTA, it was one of the update versions people posted online before 2.1 officially came out)
So I boot up holding down Power and Volume Down. So far, so good. I get to the screen that has some phone info and then HBOOT, <SEND> FastBoot Mode, <VOL UP> Recovery
I hit Volume up, and phone vibrates, goes to the Androids on skateboards, and then to a picture of the phone with a red triangle and exclamation point inside it. It just stays like that until I pull my battery. Then I can turn it back on to regular mode without any problems. However, I'm not sure what's going on.. and this would be a problem if I wanted to change ROMs.
Any help would be appreciated. Thanks
raconteur001 said:
I've poked around the forum looking for solutions but found no situation the same as mine. I'm beginning to prepare to flash a new ROM onto my Eris, so I was doing to do a nandroid backup. I have a rooted 2.1 (non-OTA, it was one of the update versions people posted online before 2.1 officially came out)
So I boot up holding down Power and Volume Down. So far, so good. I get to the screen that has some phone info and then HBOOT, <SEND> FastBoot Mode, <VOL UP> Recovery
I hit Volume up, and phone vibrates, goes to the Androids on skateboards, and then to a picture of the phone with a red triangle and exclamation point inside it. It just stays like that until I pull my battery. Then I can turn it back on to regular mode without any problems. However, I'm not sure what's going on.. and this would be a problem if I wanted to change ROMs.
Any help would be appreciated. Thanks
Click to expand...
Click to collapse
It sounds like you installed the leaked 2.1 root ROM (very early, buggy version of 2.1) and never installed a custom recovery (your information above indicates that you currently have a stock recovery).
You could verify that this is the case by checking your phone's information against this thread: http://androidforums.com/eris-all-things-root/87118-reference-what-htc-rom-do-i-have.html (it is a little crazy / scary that someone has used the 2.1 base root ROM all of this time given all of the bugs that it had ).
I *think* that you could use jcase's 1-click app (see http://forum.xda-developers.com/showthread.php?t=742228) to push Amon_RA's custom recovery onto your phone.
There's other methods too, but you might want to explore the simplest first.
Amon_RA's recovery works. thanks
scary alien said:
I *think* that you could use jcase's 1-click app (see http://forum.xda-developers.com/showthread.php?t=742228) to push Amon_RA's custom recovery onto your phone.
Click to expand...
Click to collapse
FWIW, that is correct. Even though the "Leak Root" HTC ROM is already rooted, it contains the same chmod 777 symlink business in its' boot scripts, so the jcase OneClick or the Dummies method can be used to install a custom recovery to the "Leak Root" HTC ROM. (Even though it is already a "rooted" ROM in a sense). The recovery could also just be flashed directly using fastboot, as the Leak Root ROM installs the 1.49.2000 S-OFF bootloader.
Sounds like the OP fixed his problem - somehow.
bftb0
bftb0 said:
FWIW, that is correct. Even though the "Leak Root" HTC ROM is already rooted, it contains the same chmod 777 symlink business in its' boot scripts, so the jcase OneClick or the Dummies method can be used to install a custom recovery to the "Leak Root" HTC ROM. (Even though it is already a "rooted" ROM in a sense). The recovery could also just be flashed directly using fastboot, as the Leak Root ROM installs the 1.49.2000 S-OFF bootloader.
Sounds like the OP fixed his problem - somehow.
bftb0
Click to expand...
Click to collapse
Thank you for the confirmation, bftb0 as always...
Yes, it would be nice for the OP to disclose the resolution information for the sake of helping others.
Cheers and Happy New Year's Eve Eve!
I'm not sure what information you're asking for but..
HBOOT-1.49.0000 (PB0010000)
not only did Amon RA recovery work, regular recovery works now as well (unless that's amon RA recovery also, but it looks different). Thanks for your help
in recovery it says
Build: RA-eris-v1.6.2
raconteur001 said:
I'm not sure what information you're asking for but..
HBOOT-1.49.0000 (PB0010000)
not only did Amon RA recovery work, regular recovery works now as well (unless that's amon RA recovery also, but it looks different). Thanks for your help
in recovery it says
Build: RA-eris-v1.6.2
Click to expand...
Click to collapse
I think we were looking for confirmation that you really did have the base leaked 2.1 root ROM--but it looks like, based on the HBOOT version (1.49.0000) that you actually had an un-rooted 2.1 leaked ROM.
Also, you must have run the 1-click app to gain Amon_RA's custom recovery, correct?
If you would have cross-checked the original ROM's Settings -> About Phone -> Software information's "Software version" and "Kernel version" against the information in http://androidforums.com/eris-all-things-root/87118-reference-what-htc-rom-do-i-have.html it would have made diagnosing what was going on a little easier.
Thanks for responding!
Ah. I used z4root some time ago. So i'm definitely rooted because Superuser and Wireless Tether are on my phone. I have the v2 leak: 2.26.605.4
raconteur001 said:
Ah. I used z4root some time ago. So i'm definitely rooted because Superuser and Wireless Tether are on my phone. I have the v2 leak: 2.26.605.4
Click to expand...
Click to collapse
Thanks, the v2 leak info does help .
I'm only familiar with Z4 root w/regard to how it rooted my Droid X...did it (Z4) install Amon_RA's custom recovery or did you get it by another means? (I ask this because your initial post indicated you had trouble booting into recovery and it appeared from what you described to be the stock recovery).
scary alien said:
Thanks, the v2 leak info does help .
I'm only familiar with Z4 root w/regard to how it rooted my Droid X...did it (Z4) install Amon_RA's custom recovery or did you get it by another means? (I ask this because your initial post indicated you had trouble booting into recovery and it appeared from what you described to be the stock recovery).
Click to expand...
Click to collapse
I had to flash RA recovery using the ROM Manager app
raconteur001 said:
I had to flash RA recovery using the ROM Manager app
Click to expand...
Click to collapse
Aha! Thank you very much! That's actually two very useful pieces of information (to me at least ):
1) Z4 can root an Eris without installing a custom recovery (this is the first confirmation I've heard of this)
2) ROM Manager is a good vehicle for flashing / installing a custom recovery (I don't have any direct experience with ROM Manager, so this is good to know).
Thank you again for sharing with all of us!
Cheers and have a safe and Happy New Year!
Okay, so I've seen these issues dealt with separately, but never in conjunction. Unfortunately, I am having both in conjunction.
Starting with a fresh Droid Eris, I used a one-click root to allow superuser permissions.
From there, I flashed CM7. Along with many other users, I ran into the issue where I had no data or voice signal.
I'll let you know here, that I've wiped EVERY time I did anything. This is NOT a wipe issue.
I flashed the newest radio... No luck. So, I went through clockwork's recovery and reverted back to the original 2.1 ROM. Still no luck on the signal issue. At this point, I decided to reflash CM7 and try to deal with the issue through ADB.
This is where things went wrong. The load for CM7 corrupted (I'm assuming) and gave me a nice case of Bootloop. Thinking everything was fine, (Assuming I'd do a battery pull and just go back to 2.1) I booted into the original Android recovery and NOW the damn track ball will no longer make selections. It will scroll, but not select.
Here's my question: Seeing as I can not boot fully to allow usb debugging, and I can not recover through Android (Thank you, trackball), is there ANY way to reflash the original RUU through ADB?
Thus far, I can't get passed the obvious "This device is not ready," prompt.
Any help is greatly appreciated.
FYI, adb is available when the custom recovery is booted.
what that means is that with the recovery booted you can:
1) drop a smallish (say, less than 100 MB) ROM file into /cache (e.g. "adb push")
2) create an Android command file (/cache/recovery/command) with a single line that points at the ROM file as an update
3) do a "adb shell reboot recovery"
This will cause the subsequent boot to the recovery to automatically install the ROM file you dropped in cache.
Voila. No trackball needed.
The syntax for the command file (/cache/recovery/command) will be a single line:
--update_package=CACHE:your_ROM_file_name_goes_here.zip
See this post for an expanded explanation.
cheers
[ Edit ]
Note that the above is a thumbnail sketch which requires you to fill in the blanks. For instance, wiping /data and /cache and flashing packages after the main ROM. Cumbersome, but you only need to do it once. Once you have a rooted ROM installed, you should flash a trackball-free version of the recovery so you don't need this method for every ROM you install. Instructions for that (using "flash_image" via adb) can be found elsewhere.
Scott,
Whoa! You got a lot going on there...
Okay, I don't have all of the answers here for you, but I know enough to ask a few questions that we'll need a clarification on.
1. Can you tell us your HBOOT version and whether its S-ON or S-OFF?
2. You mentioned that you've used ClockworkMod (not good , but maybe not terrible)...you also have mentioned using/having Amon_RA custom recovery. Which custom recovery do you have currently installed and can you boot into said recovery?
3. By the way, I think the voice/data signal thing is fixable--it sounds familiar to me, but I don't know the answer right off-hand and this is not your primary issue at the moment.
4. You should be able to run the RUU to restore 2.1 back to your phone. It doesn't require a working custom recovery running and/or adb. Although you might simply be asking if you can flash a ROM through adb, then the answer is yes, you can. Although you will need custom recovery running to make sure its adb server is running and that, of course, require USB connectivity (alluding to your "This device is not ready." message).
5. Usually, installing HTC Sync will install the USB drivers necessary for you to use adb. If that doesn't work for you, PM me with your email address and I'll send you about 10MBs worth of USB drivers I've collected over the last year that might help you with this issue.
6. Lastly, there is a version of Amon_RA's custom recovery available that does not require the use of the trackball. You're not really in a position to flash/install that at this point unless you have the S-OFF engineering bootloader.
I'll hold-off with additional info pending your responses to the above.
Cheers!
edit: trumped by the Master himself, LOL! [I knew you'd be along sometime soon, bftb0 ]
scary alien said:
Scott,
Whoa! You got a lot going on there...
Okay, I don't have all of the answers here for you, but I know enough to ask a few questions that we'll need a clarification on.
1. Can you tell us your HBOOT version and whether its S-ON or S-OFF?
2. You mentioned that you've used ClockworkMod (not good , but maybe not terrible)...you also have mentioned using/having Amon_RA custom recovery. Which custom recovery do you have currently installed and can you boot into said recovery?
3. By the way, I think the voice/data signal thing is fixable--it sounds familiar to me, but I don't know the answer right off-hand and this is not your primary issue at the moment.
4. You should be able to run the RUU to restore 2.1 back to your phone. It doesn't require a working custom recovery running and/or adb. Although you might simply be asking if you can flash a ROM through adb, then the answer is yes, you can. Although you will need custom recovery running to make sure its adb server is running and that, of course, require USB connectivity (alluding to your "This device is not ready." message).
5. Usually, installing HTC Sync will install the USB drivers necessary for you to use adb. If that doesn't work for you, PM me with your email address and I'll send you about 10MBs worth of USB drivers I've collected over the last year that might help you with this issue.
6. Lastly, there is a version of Amon_RA's custom recovery available that does not require the use of the trackball. You're not really in a position to flash/install that at this point unless you have the S-OFF engineering bootloader.
I'll hold-off with additional info pending your responses to the above.
Cheers!
edit: trumped by the Master himself, LOL! [I knew you'd be along sometime soon, bftb0 ]
Click to expand...
Click to collapse
Yup bftb0 is a beast at these things, lol
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
As of the time I'm writing this, there is no way to get the phone back to "Locked" once you've "Unlocked" it. The phone will show "Re-locked" if you relock it so know that until someone figures something out, Verizon WILL KNOW that you've unlocked your phone once you do it IF they bother to check and know how. It's your gamble, but to date, I've not heart of Verizon detecting root/unlock and refusing service to one person I can confirm. Said another way, you can "un-root" your phone (remove su and SuperUser), but that won't hide the more important fact that you've unlocked it. Consider this before continuing. Unlocking VOIDS YOUR WARRANTY. You accept responsibility for following this guide. Myself and other devs only provide information.
In general, here is what you will be doing:
Using the HTCDev.com site to submit your phones key and get an unlock.bin that you can use with fastboot to unlock your phone. NOTE: This WILL WIPE YOUR PHONE. I suggest using a temp-root method to first install Titanium or similar app, and do a app/data backup. This way when you're done, you can restore apps/data and be just about where you were when you started, only better.
Use the zergrush perm-root method to obtain permanent root and install SuperUser.
Install a customer recovery that will allow you to do a nandbackup and then install other roms/kernels (needed for the next step also).
Install Ziggys custom kernel which addresses some important issues for this phone and provides some other nice features.
NOTE: If you intend on flashing one of the newer ROMs ("newer" as of 2012-03-24) that require the 3.11.602.22 firmware, use Scott's directions HERE then come back and continue.
Now for the actual steps:
UNLOCKING - First visit THIS post for detailed instructions on how to unlock your device. This is required for permanent root and just about everything else following. This WILL VOID your warranty as the post says. This will also WIPE your device so again, I suggest first using THIS temp-root method so you can install an app like Titanium Backup to backup your apps/data.
PREPARING ADB - Once you have unlocked and your phone has rebooted, hit the home key to skip HTC Setup (no point doing it just yet really). Now hit, menu, settings, Applications, and check "Unknown Sources" (for good measure), then "Development" and check the box "USB debugging". I recommend then backing up a screen and un-checking "Start automatically", but that's my preference, not a requirement.
CONFIRMING ADB - At this point, I'm going to assume you already have ADB installed and known how to invoke the command because there are at least 9,999,999 tutorials online explaining this. Go ahead and open a cmd prompt and run "adb kill-server" and then "adb devices" and ensure that your device (if you see one, then you should be fine) shows up.
ROOTING - Now visit THIS thread and hit the less-than-obvious link titled "Download - OneClickRoot" to download the zip containing the tool. Follow the directions in that thread to permanently root your phone.
Boot fully into Android before proceeding.
RECOVERY
PREPARE RECOVERY.IMG - Visit THIS thread and download the attachment. Extract "recovery.img" from the zip and place it in a folder from which you can successfully run ADB. NOTE: If you haven't already, putting the adb.exe files folder in your PATH will let you run adb from anywhere. Same goes for fastboot. This makes life with Android tweaking/hacking MUCH easier.
FLASH RECOVERY 1/2 - Now "CD" into the folder (HERE you can find more about the CD command) with recovery.img and run the following command: "adb reboot bootloader". Once the phone has rebooted into the bootloader (a white screen with text menu, should say "*** UNLOCKED ***" at the top now). In white with a red background you should see "FASTBOOT USB". If so continue, if not, ask for help
FLASH RECOVERY 2/2 - The moment you run the following command, you should see a vertical bar on the upper-right hand corner of your phones screen. If so, it's working as expected. In your CMD window, run the following command "Now "CD" into the folder with recovery.img and run the following command: "fastboot flash recovery recovery.img"
REBOOT TO RECOVERY - If you have't touched the volume keys, "BOOTLOADER" is selected and pressing power will take you to the bootloader where you can then use the arrow keys to select "RECOVERY" and again press the power button to get into recovery. Otherwise, reboot any way you see fit and once running, use "ADB reboot recovery" to get into recovery easily.
KERNEL
DOWNLOAD FILES - First download the two files from THIS post (NOTE: The OP most may end up with more updated files, but as of the time I'm writing this, these are the way I suggest).
PUSH FILEs 1/2 - If you haven't already rebooted into recovery, review the previous steps and get your phone into recovery ("ADB reboot recovery" is my preference). Now "CD" into the folder containing the two files downloaded in the previous post. From here, I will use the file names as they were when I downloaded. Yours could be slightly different so adjust accordingly. In the recovery use the volume keys to navigate to the "Mounts" menu and then "Mount /sdcard". Use the Power button each time to select the menu option.
PUSH FILEs 2/2 - Now from your CMD window (the one in the folder containing the two kernel files), run the following commands: "adb push FlashMeInRecovery.zip /sdcard/" and then "adb push PH98IMGZIGGYUNSIGNED.zip /sdcard/PH98IMG.zip".
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 2/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
If you get the notorious "MainVer Error", use one of the following guides to get past the error. NOTE: Neither of these are for the faint-of-heart and the first I consider easier, does carry some real danger if done incorrectly.
Option 1 - Follow the guide HERE <-- Requires the use of a HexEditor and one is recommended if you don't have a preferred one yet.
Option 2 - Follow the guide HERE <-- Requires modification of the PH98IMG.zip you're trying to flash and sometimes this can be problematic. Either way, it provides an excellent description of why the error occurs.
FINISH - Once the 2nd kernel file is flashed and you're prompted, press power to reboot. After your phone is running again, use the following command to rename the kernel file so it doesn't cause you trouble later in the bootloader (but still keep it handy): "adb mv /sdcard/ext_sd/PH98IMG.zip /sdcard/ext_sd/PH98IMGZIGGYUNSIGNED.zip"
If this guide has helped you and you want to show thanks, just hit the "Thanks" button at the bottom of this post. It's not a donation or anything like that, just a counter used here on XDA
I will try to keep this post refreshed as newer files become available, as things get easier, or things change. If you see an error/typo/concern with these directions, PLEASE PM me and don't muddy up the thread. If YOU will do this, "I" will not only try to maintain the post, but I will also try to add/maintain an FAQ post as needed.
Btw, in case you recognize me and are wondering why I've posted here, it's because my site is dead due to childish drama, I still want to help the community and this seems the most reasonable way to do so for now.
EDITS:
20111230_1804 - Added a hint and link about the "CD" command for users who aren't familiar with "DOS" like commands.
20120101_1923 - Added a direction to boot into Android after rooting.
20120101_2325 - Added warning about unlock/relock and warranty in BIG RED text.
20120208_1709 - Added instructions on how to handle the "MainVer" error.
20120324_1636 - Added note about using 3.11.602.22 based ROMs and linked to Scott's (CleanROM) directions.
Great guide, thanks! Worked just fine and wow this thing is fast as BALLS
Using SetCPU to tweak and monitor, any clue on what the best governor is for this kernel?
EDIT: Reading original post about kernel from Ziggy, "lagfree" governor is available, using that now.
Thanks!!!!!
may i flash kernels on custom rom
or has to be stock rooted?
qudwis said:
may i flash kernels on custom rom
or has to be stock rooted?
Click to expand...
Click to collapse
this kernel is based off of the one made for gingerbread, so as long as the ROM you're running is a Gingerbread ROM, you can, or should be able to use this kernel with it.
*EDIT* I believe it may matter whether the ROM is Sense or AOSP based as well. currently we only have sense roms so it doesnt much matter, but it will down the road.
one more question.
i have cwm for recovery. since cwm don't have developer menu,
do i need to change to Amon Ra recovery?
and if i do, how do i change?
The guide is clear, succinct, and accurate. Everything worked perfectly - thanks so much.
I could've got so much more work done over the last two days if I had a tutorial like this! Untold hours have been spent combing these boards to piece together this whole process. Thanks for taking the time to do this for everyone.
Seemed to work!
I only did the recovery / kernel part since I had done the rest previously. For some reason it partially wiped my phone storage and SD card. Directories are there, but nothing is in them. No idea what happened, but oh well.
At least now I can start messing with stuff.
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
bal1985 said:
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
Click to expand...
Click to collapse
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
rainabba said:
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 1/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
Click to expand...
Click to collapse
This looks very clear and helpful. I'm not ready to use it yet, still need to study up on all this root stuff but thanks for posting.
Just wanted to point out that there may be a small and not so important typo. Both flash files are 1/2, shouldn't the second one be 2/2?
I have downloaded both files into my sd card, flashmeinrecovery.zip worked fine. The pmhimg.zip keeps saying aborted. I am running cwm, should I be running a different rom? What can I do to get the pmh zip to work?
I downloaded them via the qr codes, and they are in the download folder on my sd card. I did change the name on the second zip.
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
pwned3 said:
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Just reboot normally after flashing
sent from my cm7 rooted fire
And move the file. It will read it every time you go into the bootloader
sent from my cm7 rooted fire
Followed instructions and kernel would not flash. All steps completed without errors and still has same kernel. Any advice?
rainabba said:
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
Click to expand...
Click to collapse
so I just unistall SU from the Market? Or do I have to go in with Root Explorer and delete the file? once that is done don't I have to lock the bootloader using that htcdev guide again?
remmy5r said:
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Click to expand...
Click to collapse
Following step 7 specifically prevents you from having to deal with that. So long as the PH file exists in your sdcard root, when you go into bootloader, you will be prompted. Once your running normally, just go follow step 7 and you'll be good to go.
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
The best guide ever is in the development section, it works for your device.
http://forum.xda-developers.com/showthread.php?t=1239185
follow the guide its very easy and worked fine for me
I Return triumphant, and gentlemen, i must say you were incorrect.
The I/O edition does not give you the option to access recovery at any point, even with the Pwr+VOL DN boot.
You can put it into download mode, and certianly use ODIN to install the recovery rom, but you will have no method to actually access recovery to push zip files.
thanks to some quick self education on using fastboot, i was able to root successfully.
To those of you in a similar situation who stumble upon this thread, i invite you to visit:
http://droidbasement.com/db-blog/?p=2439
There you can download CWM in a .img format for use with fastboot.
This link is where you can download fastboot:
http://forum.xda-developers.com/attachment.php?attachmentid=596615&d=1305443483
and you'll need to install PDANet for Android to get the fastboot drivers:
http://junefabrics.com/android/
I belive you'll also need ADB installed from the Android SDK. i do have it installed on this computer, but did not use the ADB command at any point, just fastboot.
Instructions:
1. Download fastboot, PDANet for android, and the recovery image. You'll also need "Samsung_Galaxy_Tab_10.1_root.zip" found in Root.zip from the retail version instructions.
2. Copy the "Samsung_Galaxy_Tab_10.1_root.zip" to the tablet, and and power it off. Disconnect the USB connection
3. Unzip fastboot zip into it's own folder, and then copy your recovery.img file into the same folder.
4. Start the install of PDANet. It will ask you if you want to install drivers about half way through. say yes, and select "Samsung" when the time comes. it will install some drivers and then ask you to try and connect. windows may flare up and say they're unsigned. accept anyway.
5. watch this friendly video on how to start fastboot on your tablet:
http://www.youtube.com/watch?v=sR7vE4IueaU
"fastboot!"
Basically the same as the steps outlined for the retail version, but you will go to the usb icon instead of the box.
6. once the tablet is in fastboot, connect the USB cable. PDA net will recognize it as an ADB connection and try and load itself. it will fail, that's fine. Let the installer exit completely.
7. Open a command line in windows, and get it to the directory fastboot.exe and your recovery image are in.
8. run your fastboot command. i only used it temporarlily, so my command was:
"fastboot boot recovery-cwm_5.0.2.7-sam-tab-10.1.img"
9. the tablet should now boot into the recovery image presented. hooray! follow the remaining instructions from the retail version root, using recovery to load the "Samsung_Galaxy_Tab_10.1_root.zip" and reboot.
10. Once you've done all that, select to reboot. The tablet will reboot. i took the opportunity to disconnect the cable.
11. "Superuser" should now be in your apps, and you're rooted!
Extra Step: Download "Rom Manager" by clockwork from the android market, and install it. from here, opt to flash recovery. Once that's complete, you can now access recovery by launching that program and simply hitting "Reboot into Recovery"
I have no use for this myself but it's not often someone comes back and posts a complete howto on solving their own initial issue. I wish more people would do this. Thanks button clicked.
I just ran into this exact problem and only found this thread after figuring it out on my own. I figured my IO tab just didn't like having clockwork mod installed, but it certainly booted it. I nearly ruined it by accidentally wiping my rom trying to get it to boot at all. I had to repush my install files to the insternal memory using adb after I was able to boot into recovery with fastboot.
I haven't looked around too much (seeing as I only JUST got the damn thing to boot a rom) but is there a fix to that, perhaps installing the retail bootloader?
I'd hate to have to use fastboot everytime my rom doesn't boot. I've gotten used to wiping and installing roms from wherever I am on my other android devices.
I'm not familiar enough with the device to be able to give you a definite answer, but i imagine adding a bootloader from the retail version would give you the recovery option instead of fastboot.
personally, i'm a little more fond of having fastboot around right now, as it's easy enough to get into recovery when flashing things with it, and the bootloader for the I/O is unlocked... i can think of a few fun things to do in the future if i can load any ROM i want into memory, test it, and move on if it's no good... i may even give some of the ICS dailies a try thanks to this.
Always several ways of doing things... glad you got it worked out.
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
RootzFan,
that method is flashing an entirely new rom, down to 3.0, just to gain root access and open recovery so you can then return to 3.1.. it has the added byproduct of installing touchwiz.
IMHO, my way is a little cleaner as there is actually zero flashing needed, and you get to keep everything active and installed.
i recommend just going for custom roms - it comes already rooted - yBoot into recovery and flash a custom ROM
I have the IO tab myseldf and have been flawlessly running GalaxyTask custom ROM - http://forum.xda-developers.com/showthread.php?t=1340064
shane86 said:
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
Click to expand...
Click to collapse
oh, def not the best method... just saying it is nice that there are alternatives.
self delete
Fun Stuff.
sorry if i am asking a question asked for too many times already,but i can't seem to find a solution to my case,or either the thread is no longer active since the TS did not update his results,thus making me confused if he hassuccessfully or unsuccessfully rooted his atrix
i'm using atrix mb860 ofw 2.3.4.and i'm trying to install neutrino 2.2 rom gt
so here are what i had done until now:
1.rooted my atrix using Pete's One Click Root : http://forum.xda-developers.com/showthread.php?t=1258599
2.installed titanium backup and backed up batch of everything.superusered.
3.Installed cwm from market and got superusered.
4.flashed cwm recovery for atrix 4g
5.tried to install romracer using cwm.selected to restore previous roms and also chosen both wipes but failed.atrix reboots and shows "failed to boot , starting rsd mood"
what my concern is about,is just "rooting" enables me to already install roms?if it does,what did i do wrong in my steps?if it does not,please show me the way.i do not know if i should or should not flash my sbf files and bootloader
also,i read that to show that my atrix is rooted,it shold show at the top right corner during boot.but i don't see any
please help me because i really don't know what i'm doing here.i'm still new and the guides provided by the developers are for experienced people.it does not provide the detailed steps.also,please do explain some of the terms used like what is the difference between rooted and unlocked devices.
if you are too tired to explain everything all over again,then just give me the required links.i'll learn my way.btw,if you are able to give me a working link,and updated threads that would be very hopeful since some don't re-edit their first post,thus needs us to find the answer in a 1000++ replies
thank you in advance
You need to unlock your bootloader. The text you're referring to in the upper left corner of the Motorla screen is "unlocked" and it only appears after you unlock.
You can do it manually. See here.
Or automatically. See here.
You CANNOT install a CWM without unlocking your bootloader first. Rooting does not let you install ROMS, unlocking the BL does.
thanks for the reply.so that's what i'm missing.is it necessary to flash my sbf?and since neutrino rom gt changes my kernel(i think).
so after unlocking my bl,i can then install romracer->neutrino then?i'll update again and see what happens
graphidz said:
thanks for the reply.so that's what i'm missing.is it necessary to flash my sbf?and since neutrino rom gt changes my kernel(i think).
so after unlocking my bl,i can then install romracer->neutrino then?i'll update again and see what happens
Click to expand...
Click to collapse
Yes, the pudding unlocker is a small 10mb sbf file. After flashing that with RSD, you'll run the fastboot oem unlock commands.
The kernel (boot.img) is completely different from the bootloader. (if I'm reading your ? correctly).
Correct: Unlock BL>install romracer CWM> BACKUP! > install your ROM of choice
okay,this is starting to get on my nerves.i went to pudding,then scrolled down to "RSDLite/Windows Drivers/Sbf_flash"->go to hxxp://goo.gl/vfUXc link->tried but failed as it's for at&t.mine is international then.just great!
went back topudding's thread.read again..."unlock"...YES!solution for international phone!heck,this is an sbf file,what am i going to do with an sbf file?if it's just copy and paste,that will be easy.
ok,so what i really need now is a real solution to an international atrix and not at&t's atrix.or is there actually another thread for just international atrix?i just don't understand at all.please help
http://www.youtube.com/user/TheSmokingAndroid
Ck the earlier videos that he has posted on unlocking the atrix, helped me quite a bit.
FINALLY DID IT!now to install neutrino gt!thanks for all your help guys!.this guide was indispensable:
hxxp://forum.xda-developers.com/showthread.php?t=1302423
a new question : how do i install romracer?the guide did say to install itbut i don't see the app?
nvm,finally able to install neutrino.thanks a lot guys!now where's the close thread button...
no wait,again another problem!i wanna ask at neutrino's thread but this stupid 10 posts rule is preventing me.so i need to ask here.after installing neutrino,my internal memory is left with 2gb only.where is the other 8gb?when i plugged into usb,i did find them.
to note,i used cwm to install neutrino gt.the zip file was in internal.does that have anything to do with it?any way to get it back?do i need to flash neutrino again?if so,please teach me
also,how to get the market back?