Hi all! I'm really hoping that some Andriod guru out there can figure out the predicament I've gotten myself into. First a litte background info:
The other day I successfully flashed the new JI5 update to my phone. It worked great, and seems to have at least patched (not fixed) the majority of this phones shortcomings. But of course most of you already know all this.
I attempted to flash the same update to my wife's phone tonight, however as soon as ODIN finished doing it's thing the phone rebooted, and I now seem to be stuck in recovery with the following error:
update media, please wait
E:Can't mount /dev/block/stl10(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:copy default media content failed.
The process I used to flash the phone is pretty standard. Fired up ODIN, used ADB to throw the phone into download mode (Both our phones seem to be HW locked), pushed the update to the phone. The one thing I DID do differently this time was select the Re-Partition option, as I've noticed some strange issues with my phone since throwing JI5 on it. I figured that repartitioning the phone back to it's prestine state might fix the issues. I made sure to use the correct 512 PIT file, which I think I remember reading was responsible for setting up the system partitions, thus I figured I wouldn't have any problems. I've read about many others that routinely repartition their phones, so I didn't think this would be an issue. Her phone was bone stock, aside from being rooted. No OC kernals, lagfixes, etc.
I've tried to throw the phone back into download mode via adb, but it just reboots the device and it immediatly goes into recovery mode. Since the phone still boots and gets into recovery mode I'm thinking it's not bricked, but I'll be damned if I know what to do next!
So how about it, any guru's out there that have seen this problem before? Any way it can be fixed?
Update: Still borked and at wits end! Since I still apparently have the ability to reinstall packages via recovery I'm hoping that there is a way to reflash the OS by utilizing a crafty update.zip file. Based off what I've read so far, I simply need to reflash to stock OS to get things rolling again, but I can't get the damn thing into download mode! So close, yet so far away. Thank you Samsung QA! I guess this is what I get for not clockwork modding her phone prior to working on it. But still, frigging ridiculous that this company is sending out broken hardware and untested products.
If anybody happens to know a way to utilize the recovery console to flash a firmware revision (without using clockworkmod recovery), or possibly how to perform a fix action via ADB, any info you can lend to me would be much appreciated.
Bumping for the sake of my sanity.
Anyone have any ideas as to how to fix this thing? I'm a hair's-breadth away from donating this thing to willitblend.
First I must scold you for not having Clockwork Recovery Flashed, it is the first thing you do when you have root. Period. Nothing else takes priority over being able to save your phone.
Secondly I must praise you for asking this in Q&A / General, NOT DEV! I FUC*ING HATE THAT! So thanks!
Steps to fix your wife's phone:
Step 1: Download attached zip, and put on phones internal SD. (adb push update.zip /sdcard/update.zip)
Step 2: Select Re-Install Packages from Stock Recovery Menu.
Step 3: Phone may reboot, if so see step 2. If phone enters clockwork go to step4.
Step 4: Flash Rom. Flash a full rom that is flashable via Clockwork. THAT OR::: try adb reboot download from clockwork.
Step 5: Reroot phone, install clockwork recovery (rom manager on market).
Optional: If all this doesn't work feel free to purchase my Vibrant, link in Sig
Edit: Also don't just do things you don't understand, like check repartition
Thank you sir! You're a saint!
zaduma said:
First I must scold you for not having Clockwork Recovery Flashed, it is the first thing you do when you have root. Period. Nothing else takes priority over being able to save your phone.
Secondly I must praise you for asking this in Q&A / General, NOT DEV! I FUC*ING HATE THAT! So thanks!
Steps to fix your wife's phone:
Step 1: Download attached zip, and put on phones internal SD. (adb push update.zip /sdcard/update.zip)
Step 2: Select Re-Install Packages from Stock Recovery Menu.
Step 3: Phone may reboot, if so see step 2. If phone enters clockwork go to step4.
Step 4: Flash Rom. Flash a full rom that is flashable via Clockwork. THAT OR::: try adb reboot download from clockwork.
Step 5: Reroot phone, install clockwork recovery (rom manager on market).
Optional: If all this doesn't work feel free to purchase my Vibrant, link in Sig
Edit: Also don't just do things you don't understand, like check repartition
Click to expand...
Click to collapse
Thanks for the fast reply! And yes, I feel retarded for not clockworking her phone. In my defense, I thought I knew what I was doing when I ticked the option, as I had read countless threads about repartioning the phone. I think the problem is that the JI5 update is an incremental update, not a full OS. By repartitioning and flashing I think the process removed some key OS files. Or not, I'm no expert when it comes to this OS.
Anyhoo, I tried pushing the file to the sdcard, however I am getting a permission denied error message. I've verified that the directory exists via the shell command, so I seem to be having some kind of a permissions problem. The root on her phone must have been undone, as when I try to enter SU I get the same permission denied error message. Is there a way around this?
Thank you for all the assistance thus far!
So while in recovery mode, I can see both drives showing up in disk manager and windows explorer on my computer, however they are grayed out. Typically at this point one would hit the "mount" button from the dropdown menu on the phone, but obviously this action is currently out of grasp due to my problem. Is there a way to manually mount the sdcard via adb?
I kind of figured that adb pushing stuff to the SDCARD didn't require root access, as I was always able to mount the two stores without root permissions from the phone...
I'm rather curious now. Has any one tried using the adb push command to copy files to the /sdcard directory on their phone without root? Everything I've read makes it sound like this should be possible, unless the phone is just that messed up.
Any and all replies appreciated!
Related
I remember when I was looking for all this info I had to jump from board to board to board and
experience tons of trial and error when I was successful with my own device then wounded up
bricking my phone or someone elses based on other factors, or OCLF/CWM not working in recovery,
all that fun stuff.
So I decided to design this guide as a way for a person to make one stop at this guide, and
find everything you need with some tips I had to learn the hardway.
First while YES you can root/flash your phone from 2.2 Froyo official Samsung it is more complicated
and you risk a LOT more. I HIGHLY recommend doing a flash BACK to 2.1 update 1 to make your phone
bone stock to the way it was when you first bought it (Or if you bought it with 2.2 the way it was at launch.
Its a MUCH easier process and almost impossible for something to go wrong in the process. These
steps will help if you have also bricked your phone (Kinda bricked anyways)or its stuck in a bootloop.
Also while rooting is great to apply some Lag Fixes and such there really is no point unless
your going to flash a new ROM (or OS if you're new to this) because you probably don't use your
phone to utilize any of this stuff anyways.
Before you start please be sure to have the drivers working for your phone on your PC.
If you are running Windows 7/Vista and User Account Control (UAC) is enabled, be sure
to right click the Odin icon and select Run as Administrator.
DISCLAIMER:This is my contribution to the wonderful android community here that has given me
a wealth of information on this subject, and had it not been for these boards and others like
it I would not be able to enjoy my phone and the contributions made here by so many hardworking
people. With that said. I AM NOT RESPONSIBLE FOR YOU DAMAGING YOUR PHONE.
1.Back up everything in either Titanium backup or to PC (PC backup can only save Pictures etc.
not your message logs/call logs/account settings/etc.) A Nandroid backup should work equally as
well.
2.Shut Down phone into Download Mode so Odin can recognize phone.
-If phone is in boot loop or bricked:
-Plug USB cable into PC
-Take out battery
-Put battery back in
-Hold Vol Up + Vol Down buttons at same time
-While holding inster USB cable into phone
-Odin should now recognize device in download mode
3.Load Files into proper fields. (.TAR into TAR,.PIT into PIT)
4.Do not check any other boxes then defaults. You only want the PIT file and .TAR files for this.
5.Click Start.
6.Phone should begin flash process
NOTE: EVERYTHING ON YOUR PHONE AT THIS POINT WILL BE ERASED! KERNEL, BASEBAND, ROOT, ETC.
YOUR PHONE WILL BECOME COMPLETELY STOCK AS THOUGH IT WAS JUST PULLED FROM THE SHELF
IN THE UNITED STATES.
7.If process completes the phone will reboot on its own. If it gets stuck in any one process
without moving, just close the program, and repeat steps. Might take a few tries.
Once stock OS of 2.1 Update 1 is applied you can install the update.zip on the SD.
NOTE:YOU DO NOT EXTRACT THE .zip! JUST SIMPLY PLACE IT ONTO THE INTERNAL SD IN NO FOLDER.
If you're running 2.2 froyo and you were just flashed back to 2.1, then you should already have
an update.zip. Thats fine, delete the old one and replace the new one.
1.Now that the update.zip is on your phone the rest is really is. You can root your phone using
this file from your phone. Go into recovery by holding the Vol Up+Vol Down+Power button at the
same time while the phone is off. Let go once the Vibrant logo appears.
2.Select reinstall packages. Phone should reboot and you are now rooted!
If from here you want to flash a ROM over your current OS its simple.
1.When the phone reboots and you see you have SuperUse permissions you are rooted.
2.Go to the market and download ROM manager.
3.Select Install ClockWork Recovery Mod for your specific phone within the ROM manager app.
Find your ROM, Drop it into your SD the same way as the update.zip
4.Shut down your phone and boot back into Recovery Console.
5.Select Reinstall Packages again. This should Install ClockWork (CWM) OVER your recovery console.
If it doesnt take the first time just do it again, it will take you to a different color
console.
6.Once in CWM select the item using the Vol Up or Down buttons and power to select on Install
Zip from SD card.
7.Then pick Choose/Select .zip to Install.
8.Find your ROM, Select it. Select Yes to install.
9.WHAMMY your device is now installing the ROM and you have a flashed and rooted super android phone
on steroids.
Hope this helped.
---Giddy Ninja
FILES
http://files.androidspin.com/downloads.php?dir=androidspin/samsung/vibrant/&file=T959UVJFD.tar<---SGH-T959 JFD Image
http://files.androidspin.com/downloads.php?dir=androidspin/samsung/vibrant/&file=s1_odin_20100512.rar<---512 PIT File
http://files.androidspin.com/downloads.php?dir=androidspin/samsung/vibrant/&file=Odin3.rar<---Odin Application
**References used to build this tutorial when I F**ked up my own device**
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
http://forum.xda-developers.com/archive/index.php/t-810442.html
http://board.teamwhiskey.com/viewtopic.php?f=29&t=636
http://androidspin.com/2010/08/04/all-about-root-for-the-samsung-vibrant/
http://forum.xda-developers.com/showthread.php?t=849028
http://forum.xda-developers.com/showthread.php?t=991267
http://forum.xda-developers.com/showthread.php?t=732458
Good guide for noobs
Sent from my SGH-T959 using XDA Premium App
Good post I have and will be linking it to some ppl with problems thought you deserved your first thanks lol
Thanks for the responses and any feedback or critique on where/how I can make this guide more accessible is appreciated (PM please)
I wanted this to help people who are new and scared. lol
The guide that s15274n has is like the bible to this. but I know sometimes that much information can be either overwhelming or confusing to some.
So hopefully this helps out some people!
Thanks for the post man. The more ways to help the better. Mine has a ton more detail, but some may not want / need that much.
s15274n said:
Thanks for the post man. The more ways to help the better. Mine has a ton more detail, but some may not want / need that much.
Click to expand...
Click to collapse
And that is EXACTLY what I was hoping to accomplish. Sadly though I didn't stumble across your thread last night when I had soft bricked my brothers phone and was doing a million google searches to find the work around on his boot loop frenzied phone (Recovery console was even corrupt).
So after what seemed like 1000 snipits from different articles I was able to mostly compile this. And then throw in some warnings for future rooters/flashers.
Had I known Samsung's own 2.2 release was going to be so AWFUL compared to 2.1 I never would have upgraded. But then again if I probably never would have flashed/rooted. haha. Oh well what can you do.
update.zip signature verification failed
the update.zip doesnt work in my DEfy
e: signature verification failed
installation aborted.
searching in xda developers i found this thread...
http://forum.xda-developers.com/showthread.php?t=995131&page=4
i dont really understand what is this update.zip for... yours is 600Kb and this one is 140Mb! this file is just to root the mobile right? I am a bit worry about to use this file... maybe i will get a Defy brick... hehe
any suggestion?
thanks a lot
jose
jacortijo said:
the update.zip doesnt work in my DEfy
e: signature verification failed
installation aborted.
searching in xda developers i found this thread...
http://forum.xda-developers.com/showthread.php?t=995131&page=4
i dont really understand what is this update.zip for... yours is 600Kb and this one is 140Mb! this file is just to root the mobile right? I am a bit worry about to use this file... maybe i will get a Defy brick... hehe
any suggestion?
thanks a lot
jose
Click to expand...
Click to collapse
You are in the vibrant forms you need to go to the xda defy fourm.
http://forum.xda-developers.com/forumdisplay.php?f=852
Yea sorry I can't help you out. As stated above this is a Vibrant forum. So don't use that update.zip. Only two things I can tell you are go to the link above, and im sorry you bought a Motorola. Lol.
Sent from my roided out Vibrant.
Sir... i have faced a problem inmy swipe konnect plus smartphone. When i try to power on my phone it automatically goes to recovery mode. Service center says that phone cannot be flash.. so i decide to flash manualy
. Plz help me.. my phone unable to open... how to root my phone .. please help me...
I've spend much of the day trying to root and then flash my new Optimus V. For some reason I keep running into snafus, even after rooting two Eris phones and a Nook color without too much difficulty. Would REALLY appreciate the group's assistance.
After much trial and error, I finally got root using SuperOneClick.
After that, I first tried to use adb to install the asop ROM per http://forum.xda-developers.com/showthread.php?t=962862 , but would always get stuck on the blue bootloader screen. By trying to fix that, I got stuck in a clockworkmod recovery loop. I finally got out of that by doing a flash_image of the stock ROM via adb. But then, the google market, and hence my google apps (including clockworkmod) was gone.
So now I'm stuck without access to clockwork mod, and a broken stock rom/interface (with no market access.) There may be a way to launch CWM even with the vashished google apps, but I'm not sure what it is...
Here is what I do have readily available in my "toolkit":
-root still working (via superoneclick);
-Root Explorer (having manually installed the Amazon marketplace apk);
-abd access to my 4g SD card;
-a backup 4g SD card, should one prove helpful.
My goal is pretty simple: to get a good custom rom (probably ASOP) with a fully functional suite of apps, and to MAKE SURE that the other corruption I've unwittingly done to my phone's data is complete eradicated.
I apologize for the jumbled nature of this post. I'm sure I'm leaving some diagnostic stuff out that would be useful--please fire away and I'll be more than patient about trying to clarify.
THANK YOU in advance for any help you can offer!
polphi said:
I've spend much of the day trying to root and then flash my new Optimus V. For some reason I keep running into snafus, even after rooting two Eris phones and a Nook color without too much difficulty. Would REALLY appreciate the group's assistance.
After much trial and error, I finally got root using SuperOneClick.
After that, I first tried to use adb to install the asop ROM per http://forum.xda-developers.com/showthread.php?t=962862 , but would always get stuck on the blue bootloader screen. By trying to fix that, I got stuck in a clockworkmod recovery loop. I finally got out of that by doing a flash_image of the stock ROM via adb. But then, the google market, and hence my google apps (including clockworkmod) was gone.
So now I'm stuck without access to clockwork mod, and a broken stock rom/interface (with no market access.) There may be a way to launch CWM even with the vashished google apps, but I'm not sure what it is...
Here is what I do have readily available in my "toolkit":
-root still working (via superoneclick);
-Root Explorer (having manually installed the Amazon marketplace apk);
-abd access to my 4g SD card;
-a backup 4g SD card, should one prove helpful.
My goal is pretty simple: to get a good custom rom (probably ASOP) with a fully functional suite of apps, and to MAKE SURE that the other corruption I've unwittingly done to my phone's data is complete eradicated.
I apologize for the jumbled nature of this post. I'm sure I'm leaving some diagnostic stuff out that would be useful--please fire away and I'll be more than patient about trying to clarify.
THANK YOU in advance for any help you can offer!
Click to expand...
Click to collapse
Boy, First of all don't panic. Without bricking you can't learn.
Second for Root you can use Gingerbreak. This should work. http://forum.xda-developers.com/showthread.php?t=1044765
for Flashing on all use custom recovery tool. And its like one two three from your phone only using terminal apps. Here is the guidehttp://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
After entering in Custom recovery mode you can do what ever you want to do. Flash rom as per your desire.
have you flashed clockworkmod recovery before?? if yes access it using the three button combo....you can flash any rom you want from recovery....
hit the thanks button if i have helped you.
sajjan said:
have you flashed clockworkmod recovery before?? if yes access it using the three button combo...
Click to expand...
Click to collapse
Alas, after restoring the stock, the three button combo brings up not clockworkmod, but "Android system recovery <3e>", which *only* allows:
reboot
apply sdcard update.zip
wipe data/factory reset
wipe cache partition
Since I don't have an update.zip file that works, I can't seem to get beyond this. When I tried renaming a custom rom recovery file update.zip, I got a signature mismatch, which makes sense.
First, thanks to both sweetbinodray and sajjan for the replies.
sweetbinodray said:
Boy, First of all don't panic. Without bricking you can't learn.
Click to expand...
Click to collapse
Hehe, that's similar to what I keep trying to tell myself.
Second for Root you can use Gingerbreak. This should work.
Click to expand...
Click to collapse
I have root, even have root explorer working via Amazon mktplace. (I shouldn't need or want to re-root, should I?)
for Flashing on all use custom recovery tool. And its like one two three from your phone only using terminal apps. Here is the guidehttp://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
After entering in Custom recovery mode you can do what ever you want to do. Flash rom as per your desire.
Click to expand...
Click to collapse
When I follow that guide, I'm linked to an updated thread which asks me to enter shell (no problem) then use the following command as first in a series:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
that results in "mount: operation not permitted".
Basically, having (regrettably) tried to to start from scratch by reflashing stock, I keep running into these permission snags.
Seems like if I could get to the CWM recovery screen, or figure out a way to trick the stock recovery screen into accepting a different update.zip, I'd be OK.
Then again, perhaps that's making things too complicated?
TIA once again!
Also, this looks like it might work, but I can't seem to get the validation email necessary to validate a board membership, which appears necessary to download the Quick Boot file.
polphi said:
First, thanks to both sweetbinodray and sajjan for the replies.
Hehe, that's similar to what I keep trying to tell myself.
I have root, even have root explorer working via Amazon mktplace. (I shouldn't need or want to re-root, should I?)
When I follow that guide, I'm linked to an updated thread which asks me to enter shell (no problem) then use the following command as first in a series:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
that results in "mount: operation not permitted".
Basically, having (regrettably) tried to to start from scratch by reflashing stock, I keep running into these permission snags.
Seems like if I could get to the CWM recovery screen, or figure out a way to trick the stock recovery screen into accepting a different update.zip, I'd be OK.
Then again, perhaps that's making things too complicated?
TIA once again!
Click to expand...
Click to collapse
Ok what i can suggest you is do manual set up for custom recovery using terminal apps. Here is the guide http://forum.xda-developers.com/showthread.php?p=15185778#post15185778 and start form install terminal emulator. And write following commands.. its like one to three....
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
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.
(i made sure to do a backup)
Let me sum up what I have done:
I've managed to follow a guide on a wiki(I lost the link however, since I ATTEMPTED to give up on this) that involved me downgrading my firmware, then do some steps to install cyanogen 1.4. Afterwards, I got to step that required me to rename some file to update.zip. I followed that step and noticed my computer didn't convert the file to a zip file(it remained as a img file) but continued anyway while finding that odd.
Afterwards, cyanogen tells me that it cannot find the zip file. I've search most of google and a bit of this site, and i've seen various solutions that failed me such as:
-renaming the update.zip to update
-using android sdk(which i have no clue on how to use)
Anyways, finding out that I was foolish to do all of this without prior knowledge, I decided to go back to my original firmware. However, on the phone's reboot, cyanogen came up again for some reason, and didn't let the update be applied.(I don't recall the error)
Anyways, I selected reboot and got to my phone's main menu then some music started playing automatically. I should note, before I did the update, I placed all of my backed up data(while still having the original copy on my pc) on my phone so it might've been some music that the original owner had. Now, on the menu, i'm getting this error "The process android.process.acore has stopped unexpectedly. Please try again." all the time. Since this error constantly pops up, I can't do anything.
So if you managed to read my long and boring story, let me ask one question:
How do I get my phone back to normal if rooting is impossible at this point?
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Dataslycer said:
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Click to expand...
Click to collapse
It's on 1.5 currently. Also as a little update:
I fixed the "not being able to do anything on the menu" problem by doing a factory reset. Afterwards, I learned the SDK a little bit more and have the tools, pc driver, and fastboot on my pc. However, i'm getting the error:
FAILED (remote: not allow)
Just a bump. I need all the help I can get on this one. Even a premade update.zip would help me GREATLY.
One last bump. I promise.