Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
Hi All,
So, I tried to flash Cyanogen mod last night using the instructions here: http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide. I was coming from a BIONIX ROM that flashed fine.
Anyways, the phone went into a reboot loop in the recovery screen and I foolishly just held the power button until it stopped. When I turned it back on it was broken. That is, now all it does is display the white Vibrant logo in the middle of the screen with the smaller Samsung logo below it. If I hold the power button for about 8 seconds the screen goes black for about 2 seconds and then comes right back up to where it was. I can't seem to even turn the phone off any more. It just stays on that screen permanently unless I hold the power button, in which case the screen is off for 2 out of every 10 seconds. Yanking the battery of course turns it off, but putting it back in immediately returns it to the state I've described.
I've scoured these forums and tried every button press + battery state + cable state + SD card/SIM state combo suggested, but the phone won't go to download or recovery mode. I found one thread describing the exact same problem. The OP said he'd try a jig and then disappeared without any further updates. I'm going to try to get my friend to make a jig using one of these sets of instructions
http://forum.xda-developers.com/showthread.php?t=819551
http://factoidz.com/how-to-unbrick-your-samsung-vibrant-galaxy-s/
but until then my questions is: does anyone have any experience with this problem (can't even turn the phone off)? If so, do you have any recommendations? Did a Jig work?
keep trying to get to download mode, pull battery, plug usb in to computer and to the phone, while holding both volume up and volume down pop in the battery. People have tried hundreds of times with it not working and then all of a sudden *bam* download mode.
So... my friend made me a jig and it works in that I can see the shoveling droid indicating download mode. However Heimdall/Odin won't recognize my phone. Heimdall's zadig utility won't locate the phone either, even with the cable plugged in. I'm, once again, stumped.
Just an update; I've tried Odin on three different computers, two Windows 7 (64 bit) and a Mac (with Heimdall). None of them seem to recognize the phone. Device manager on the Windows 7 machine does not update when I plug the phone in (in Download mode via the jig or not) and I can't find anything about Samsung in it anywhere. However I have installed the Samsung drivers; a few different sets I've found around the forums. I've also tried a couple utilities like the Vibrant toolbox and one click unbrick. Nothing seems to have any effect. I was so hopeful when the jig worked and got me to download mode, but now it's seeming I'm actually bricked. Has anyone seen a phone that could get to download mode but still be bricked? Oh, and I checked the cable using a friend's phone; her Mac recognized her phone using the cable. Haven't tried her phone on my Window's machines though.
Once again, any help is more than appreciated.
Have you tried to see if adb is working? If it does then try adb reboot recovery? If it works there is a file I can post for you later (is in my pc) that can restore your sbl.bin and fix your download mode problems.
Thanks for your help everyone, the problem was apparently resolved by a new cable; which is strange because the old one works for data transfers... just not for flashing apaprently. :S
Hello all.
Today, I tried to root my TELUS Samsung Galaxy S Fascinate by using Odin and CWM3-Voodoo-blue.tar.md5. I received a "FAIL!" message, so I pressed Start again, which yielded nothing. So, I removed the USB cord from the phone and tried to boot it up. Nothing happened. I tried to use cwm-recovery-ALL.tar, but, again, I received a "FAIL!" message, and ended up with nothing.
It seems, at the moment, the phone can boot up in download mode (Vol Up + Vol Down + Power). However, the screen appears filled with randomly coloured pixels, and nothing else works on the phone. Is there a way to recover my phone from this state?
I'm going to sleep right now, so I won't be able to reply right away, but I'll check replies as soon as possible.
EDIT: Now, it seems as if the screen isn't booting up at all. However, I can still see the download screen with Vol Up+Vol Down. I don't think the phone was rooted at all, so I'm thinking of sending it back to Samsung so they can fix it. Is there a way to check if a phone is fully rooted or not?
I tried to Unroot my Galaxy Tab 10.1 LTE last night and think I may have bricked my tablet. I used the instructions here on the XDA forum which had a link to all the Stock ROM's in one place. I got the most recent one and the only one for USA but it said it was for the model 7510. I didn't think that would be a problem since the USB drivers I installed on my PC were also labeled as being for the 7510 and they worked.
This tablet is the SCH-I905. Now I can't get it to boot at all. Gets stuck in a boot loop. Shows the Samsung logo, then resets and does it again. I can't get it in recovery mode either. Goes to a black screen and hangs.
Using the normal process to get to Download mode doesn't work. Holding Power and Volume Up, then letting go of the Power button, then pressing Volume Down and then Up. That's one weird thing. I can get to the option screen that shows the Download and Recovery mode options. Normally I would hit the Volume Down button to select Download mode and on the screen it says to press Volume Up to continue or Volume Down to cancel. If I press Volume Up it goes to a black screen and hangs. If I press Volume Down I get the Odin Download screen that says Waiting on USB cable.
That screen doesn't look the same as what I normally see but I'm not sure what's different. I didn't memorize each line of text. I just know there's not as much text there as there usually is. My PC will not recognize the tablet no matter which USB port I try to use and the tablet doesn't recognize that the USB cable is plugged in. I had no problem with the USB connection before I flashed the 7510 stock ROM.
So, if I cannot get to recovery mode and I can't get Download mode to work so I can use Odin to flash a different rom then is this thing bricked or is there something else I can try? I am about to try using my laptop and its USB ports but I don't think that's going to make any difference.
BTW, I have since found the correct 'stock recovery rom' at droidbasement.com and downloaded it to my PC. I just need to get on the tablet somehow.
Many people have your problem. I have my Lte verizon bricked as yours. The problem is demaged bootloader, only nvflash can fix it but actually our bootloader is locked and we need a hex key called sbk. At least we have to wait that somebody hack our tab from the basement. For now we can only search and share result.
pickupcash said:
I tried to Unroot my Galaxy Tab 10.1 LTE last night and think I may have bricked my tablet. I used the instructions here on the XDA forum which had a link to all the Stock ROM's in one place. I got the most recent one and the only one for USA but it said it was for the model 7510. I didn't think that would be a problem since the USB drivers I installed on my PC were also labeled as being for the 7510 and they worked.
This tablet is the SCH-I905. Now I can't get it to boot at all. Gets stuck in a boot loop. Shows the Samsung logo, then resets and does it again. I can't get it in recovery mode either. Goes to a black screen and hangs.
Using the normal process to get to Download mode doesn't work. Holding Power and Volume Up, then letting go of the Power button, then pressing Volume Down and then Up. That's one weird thing. I can get to the option screen that shows the Download and Recovery mode options. Normally I would hit the Volume Down button to select Download mode and on the screen it says to press Volume Up to continue or Volume Down to cancel. If I press Volume Up it goes to a black screen and hangs. If I press Volume Down I get the Odin Download screen that says Waiting on USB cable.
That screen doesn't look the same as what I normally see but I'm not sure what's different. I didn't memorize each line of text. I just know there's not as much text there as there usually is. My PC will not recognize the tablet no matter which USB port I try to use and the tablet doesn't recognize that the USB cable is plugged in. I had no problem with the USB connection before I flashed the 7510 stock ROM.
So, if I cannot get to recovery mode and I can't get Download mode to work so I can use Odin to flash a different rom then is this thing bricked or is there something else I can try? I am about to try using my laptop and its USB ports but I don't think that's going to make any difference.
BTW, I have since found the correct 'stock recovery rom' at droidbasement.com and downloaded it to my PC. I just need to get on the tablet somehow.
Click to expand...
Click to collapse
Did you solved the issue?
Please share ..., i face the same problem now ...
regards,
erwien.
Did you solved the issue.
share me......i face the same problem now
.
.
.
.
.
.
.
.
.
.
.
.
help me plz