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
Related
I rooted my LG recently to get rid of the crapware that was on by default. But, of course, it wasn't enough for me. I tried to flash a new ROM, and everything went to hell. Now the boot screen won't go past the LG logo. Does anyone know how to reset the device back to factory standard?
Hard reset doesn't work (home + volume down / up + power)
Windows/Linux doesn't see the plugged in device.
adb doesn't see the plugged in phone
I tried to put cyanogenmod on, which was probably a bad idea. I've heard that this problem may be irreperable, and I just want to see if there's any way to avoid having to try and deal with Verizon.
Before flashing (using rom manager), I made sure to choose the backup the current rom option. I've heard that I should be able to restore that backup, but there's no way to actually connect to the phone at the moment.
Any help would be appreciated.
EDIT: I've gained access to the SD card by plugging it into an external reader. I can see the recovery image that clockwork made. How can I get the phone to boot into it?
theevan117 said:
I rooted my LG recently to get rid of the crapware that was on by default. But, of course, it wasn't enough for me. I tried to flash a new ROM, and everything went to hell. Now the boot screen won't go past the LG logo. Does anyone know how to reset the device back to factory standard?
Hard reset doesn't work (home + volume down / up + power)
Windows/Linux doesn't see the plugged in device.
adb doesn't see the plugged in phone
I tried to put cyanogenmod on, which was probably a bad idea. I've heard that this problem may be irreperable, and I just want to see if there's any way to avoid having to try and deal with Verizon.
Before flashing (using rom manager), I made sure to choose the backup the current rom option. I've heard that I should be able to restore that backup, but there's no way to actually connect to the phone at the moment.
Any help would be appreciated.
Click to expand...
Click to collapse
LOL wow i just did the same thing ... i am "was" experimenting with the optimus v cyanogen rom and now im stucc at the skate droid screen.. any help would be nice
msg me for help got my self out of it
u got out that situation? i installed a app and my phone needed to reboot now im stuck
I need help. Vortex stuck on LG logo after i flashed a rom using rom manager!
Please Please help!
infamousr60z said:
msg me for help got my self out of it
Click to expand...
Click to collapse
Consider posting how you did it here for everyone to see.
naenee said:
Consider posting how you did it here for everyone to see.
Click to expand...
Click to collapse
Yes, please do post it. I attempted the LOL 1.4.2 rom for Optimus One and am now in this same situation. I have a working rom on my sd card if I could just get to the recovery screen.
[Solved!]
s3rvant said:
Yes, please do post it. I attempted the LOL 1.4.2 rom for Optimus One and am now in this same situation. I have a working rom on my sd card if I could just get to the recovery screen.
Click to expand...
Click to collapse
I read a few posts mentioning that they were able to reset their phone using their ac adapter, but I hadn't any luck trying it that way, until a good friend of mine used some google-fu to determine that the order in which you do things matters! Here's the steps I had to take:
Remove battery from phone
Begin holding power, volume down and home
Plug phone into ac power WITHOUT LETTING GO OF BUTTONS (wasn't easy for me either)
Phone should boot into recovery (in my case the custom recovery)
You can let go of those buttons now
Install battery
Flash your phone and rejoice!
THANK YOU! The part I wasn't getting was the plugging into A/C while holding the buttons down...you're a lifesaver!!!
This did not work for me. I tried putting the phone into recovery mode, but it still just booted up as normal. I'm running out of ideas and patience here...
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Lgtools
estoy en la misma situacion, yo cuento lgtools de Setool Box3, la cual soporta lectura y escritura de sistema de Lg vortex vs660, pero no logro que me lo detecte para cargar firmware completo, mi problema fue que flashe el recovery desde el ROM MANAGER y se queda en el logo.
I recovered my friend's phone using the following procedure
I just fixed a friends phone so I thought I would share in case it helps anyone. This is for the LG Vortex on Verizon. Might work for other carriers.
Download and install the Vortex drivers from LG's mobile support site www dot lg dot com/us/support/mc-support/mobile-phone-support.jsp
Download and install the LG Mobile Update utility www dot lg dot com/us/support/mc-support/mobile-phone-support.jsp
Run the LG Update app and make sure your phone is up to date. You can also try the Recover option if it can't update. This phone's firmware was up to date.
Install the Android SDK from google.
Access backdoor recovery through ADB
Plug phone in to laptop usb
Press and hold down the volume down key, the home key, and the power key at the same time. Keep them pressed until the screen goes black then you can release. If it goes in to some other visible recovery you can simply skip some of these steps
At this point your computer should start to recognize the phone and go through a series of driver installs
Once that is complete you should be able to go to the command line and enter the ADB shell
Follow the procedure at the following link to get the clockworkmod recovery installed
androidforums dot com/getitnowmarketing/330813-all-one-recovery-thread.html
Once you are able to boot in to clockwork, immediately do a backup. Then clear your data, cache and dalvik cache, then reboot. This won't always work, but many times it will allow you to boot a ROM that gets stuck booting (like this phone). If that doesn't work then just go back to recovery and utilize a manual ROM flashing procedure you can find on many forums.
This process worked great on this phone so hopefully someone else may have similar luck.
Sorry for cutting up the links, i'm new to the forum. Just replace the "dot"s with . obviously.
Try this worked for me
Here's a different method of unbricking your vortex V660. With limited support and methods for this device it seems to make everything more complicated in finding a soluttion around certain but complex problems. I tried to use some of the other metheds listed on android central and XDA...such as, taking the battery out, holding home, vol -/+ and power key at the the same time the phone back in while it was connected to the computer. I wasnt able to get anywhere with these methodes,I also thought qbout trying the unbutu method to unbrick it then I thouht that was to much of an effott. I read all the comments and differnt methods and decide it wasn't worth the risk, I re-woked a different method for unbricking, there's prob about a 90% possibility of it working for your LG.This just happenes to be my own solution or workaround if you find yourself screwed like i did with no type of support.
The reason this didn't work was because I didn't have cwm installled nor did the phone have the original firmware installed, my mistake, I wiped that off too, happenes when you have to much to drink lol, the hard reset buttons were a no go as well since they take you into cwm or the orignal firware from verizon {all mine did was take me to a black screen because there was nothing there for it to load.} Some how or another all was wiped clean and I was in a catch 22 while being bricked. I found the vs660 recovery firmware but I knew i really didn't need to install it so i didn'nt.The bricked happened after I installed Titanium Backup then uninstalled launcher pro so then I restarted and got to the point where the ring Fire or boot animation was trying to load ,and it just just hung there. I don't care for the app launcher pro I would rather use awd launcher, if u haven't noticed you have to pay for the pro version of launcher pro just to rezize widets, so im wondering why this app was added to the Rom Cyan7.2 in the first place. So with no cwm, no stock image, and no way to make an sdcard boot into m to unbrick it my hopes and last resort were to pray that.I had usb debugging enabled.
First thing you have to install is called jdk-7u3-windows-i586] the other file called installer_r_windows wont't allow you to install until the install of JDK is complete.It'd ok to lauch the installer-r26-windows first because it ill drnf you directly to the site to downloadthe JDK file. Install these two programs first, (google how to ADB tutoria if needed? So after downloading that you will need to download the right drivers (for the voerex) Software name (Driver_WHQL_ML_Ver_4.9.7_All_Win7_LGEAll)(Google Search It)} There's 1 other thing we to have to do before seeing if your decice is listed in ADB. We need to add a line to the Envioronment Varibles section under System Variables at the bottom. Here's how to get there in Win7, right click on my computer, advanced tab, at the bottom Environmental Variblesm, click itlook down under system variables and scrooldowm until you see something called Path and add this line to end of it, ofcourse clickit edit then copy and past his line including the semicolon ;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools now save it amd exit. The reason this is done is so we won't have to contantly navigate through cmd prompt to the directory and list commands. This is prevent you from have to navigate to the folder evertime u want to run the program or any cmds. Now that were all setup lets connect to you phone's data cable to the pc and the phone, and again make sure abd debugging is enabled. Settings, applications, development, the check in the box for debugging, if it's not enabled you will get the turn on usb feature your phone so not what we want. Now opem the cmd prompt run the cmd cd.. then cd.. now you should C:\>, you can run the cmd adb devices now hit enter and you you see a long 14 to 16 digit # then that means your devices is succesfully connected and talking to your PC.That long # should be your MEID HEX# to your phone if you dont see that and you see somethine else then go back though the guide to see if you missed something during setup. If setep properlly in the cmd prompt type adb devices and your phone will automactically show its long#, after that type the cmd adb reboot at which point through cmd promt the device will reboot itself. Here a little secret just because you don't have youtr verison's orignal firmware nor a working ROM on you phone such as froyo 2.2.1 or 2.2.2 doesn't mean anything, you are still rooted and wont have to downgrade to 2.2.1. Side note ( z4root didn't work for my lg vortex, I tried gingerbreak 1.10 and later gingerbreak 1.2 which both worked just fine, z4root just hung on my phone, sry i bounced off topic but i took me 24 hrs of troubleshooting till I got it back up and running.
This method I would say this only applies to the ones that don't have cwm installed on their internal drive it acccidently wiped the original firware off their phones and don't have anything to boot into. I don't have the orignal verizon stock installed, essentially you hit the same buttons on the phone to do a hard reset or to boot into recovery as you normally would. If you neiher on your phone then ADB is your saving grace. Another tutorial I seen was something about installing ubuntu lunux, it just seemed liked to muck work for me, plus I didn't want linux on my box anyways, not til im ready for building a linux kluster later.
let get started...go and download the Adb software which is called Android-debug-brigde...you will also have a visual demo to guide you through the setup) (ADB file) name installer_16-windows,install this this file last to the root of C:/ once done its location will look like this c:\android-sdk-windows ( this is important to make sure you extract the exe to C:/android-sdk-windows (you can take advantage of youtube's a great resourse for viual walkthroughs} or google it,.i have had to do i know's our there , well if you more of a reader search google or xda it will breakdown the core or the installing of the actual files can't post links here but you have to post a minimum if 8 tines b4 you can post links outside this site.
Once all that's setup you need to confirm that its linked properly. Phone off or on during this process I wouldn't think it matters,my devices were on, so conntect you data cable to you usb port and the other end to your phone where you normally power it. This is the time you better hope USB Degugging is enabled. If it is you will see the little Android character and something that looks like a usb icon in the status bar of your phpne, so if you pull down your status bar is will tell your if you are in use debugging mode,. in the status bar depending on where your bricked. if you are in a booploop all its going to do it make that noise of connecting and disconnting. you may have to find fifferent approach to fix it, only solution I can give you if to try home, vol +, and power down til you get a black screen and hope it hangs there there long enough to so you clear it. So it this aproach words on a bootloop let me know in the comments.
Once everything looks good open up your device manager
Just under your computer mame u should see somethig called ADB Interface
under that from the drop arrow you will see android plactform sooner single ADB Interface, click on that and you will see android plattform sooner single ADB Interface, then under modems you will see LGE Android Platform USB Modem, and last at the bottom your youw will see universal serial bus controllers, select that and you should your see LGE Android Platform Composite USB Device, If you see all that that your 100% convered
Now to get your phone out of that nasty brick and we don't need need any firware or Roms to do it...
Open cmd prompt, type cd.. then cd.. again now your in C:\>
now type cd android/sdk/system (note the CD just means change directories) now were in the folder called c:\android-sdk-windows
From this directory is where were going to run our commands since we can't do it in cwm.
type wipe system and hit enter
wipe system you will see a alot of errors like it didnt do anything but that's ok next step
type wipe data hit enter
once done pull cable reboot phone wait to it to come up to where to you have to touch the andoid like your setting up the phone for the first time again, warming u more that lickly will get an FC during setup and it will brick again on the same screen. Repeat wipe system and wipe data again, the gp though the setup on the phone again, if have have another FC one last time so again wipe system then wipe data, this time there shouldn't be anymmore FCs, I have to go through wipe system and data 3 times b4 the FC's stooped and I will able to to to the activaton screen > My phone is a refurb so if would let me past the activation screen this time as when im loading up in CM7. last issue I faced was the accivation screen, Now I did some reading on this and there are a couple of thing you can one of which worked for me., You can tap the four counrers in the clockwise direction which didn't work for me, or what did, I click activcate then entered *228 then hung up, avtivate again *228 hungup, then activate again,*228 hugnup and this time I was able to skip activation anb and was again to load cwm and flash my phone, so its not longer bricked and I dont have to worry about the avivation all though it will comes up U can stip it and It wont keep me from me phone, I have VIOP setup over my 4g LTE, any questions about this type hack just let me know, ( I have an 18 Page Paper about how it works how to set it up, its free and no download charge for the APK) and I will post it. Forwaring the paper 18 pages long and pretty in depth, I dont explain the backend of how it works but just a little, its mainly the frontend and to set it up and all the routing.
I also have video demonistrations on youtube for bypassing the registration of your Nook Color
Channel is under wudamnify
Vortex sux
Okay ... so my vortex is nothing more than a paper weight at the moment. When I turn it on, the LG screen comes on for 3 seconds, then the screen goes blank, then it starts over again. I can't turn it off after it starts its boot loop. I have tried using the recovery keys, and nothing. If I plug it into the computer it will turn on and do the loop over and over again, and i still cant power off. I have a 4gb micro with cwm recovery, but i do not know how to get this phone to boot into the cwm recovery. your help would be appreciated.
Here's what worked for me
corydespain said:
Okay ... so my vortex is nothing more than a paper weight at the moment. When I turn it on, the LG screen comes on for 3 seconds, then the screen goes blank, then it starts over again. I can't turn it off after it starts its boot loop. I have tried using the recovery keys, and nothing. If I plug it into the computer it will turn on and do the loop over and over again, and i still cant power off. I have a 4gb micro with cwm recovery, but i do not know how to get this phone to boot into the cwm recovery. your help would be appreciated.
Click to expand...
Click to collapse
I was in a similar situation and was able to get to recovery by taking out the battery, holding down the buttons required to get into recovery and then while holding down the buttons, plugging the phone into the wall charger. Once it was in recovery I put the battery back in and flashed back to a known good rom. Not sure why this worked over just turning it on normally, but it's worth a shot.
Hello all. I'm a brand-noob (my phrase, thank you) here.
I have received a Verizon HTC Eris phone that boots to the red triangle with exclamation point (three droids on skateboards prior to the triangle screen). I have no information on what was done on this phone prior to my receiving it. I have read here that the three droids means that it has been rooted, and that the red triangle means a stock recovery is on it.
I can only "Up Volume + Power" to get this - "E:Can't open /cache/recovery/command". Other than that, I can't seem to get to anything else on the phone.
Now, upon connecting via usb to my computer (Windows 7), I can get Windows to recognize the "Android Phone", but not specifically an HTC Eris. I do not have HTC Sync installed. I have used ADB to root another phone (MyTouch), but this phone does not show up when I check for devices via "adb devices".
I am hoping someone can offer some simple steps that I can do to work towards fixing the phone. Thanks everyone for your time. !
This may help you:
http://forum.xda-developers.com/showthread.php?t=992916
Good luck.
Thanks for the reply phone_cell. I had already read/seen that post.
I cannot see any boot information at all, it shows the skateboarders, then the red triangle. The phone shows up on my computer, but only as an "android storage device". I'm not sure how I can check anything via my computer. I have installed PDAnet prior, and read that it should have installed the phone drivers. ? I installed HTCSync on a different computer and it doesn't see the phone.
If there is no way to fix this phone, then I understand. I would like to think that there are ways (standard methods ?) to check and/or re-install a phone (any phone) back from something like this. ? ...Thanks again for your time and expertise!
I was happy to try to help you. I recommend you send a PM to bftb0. If your Eris can be brought back to life, bftb0 will know what to do.
Bummer. bftb0 does not receive private messages, or at least not from me. Maybe someone could relay the forum post.
I am still digging and digging to try and figure something out. If I could get my computer to communicate properly with the phone, I'm sure I could re-install/fix the boot problem.
Anyone have ideas on how to install a usb device that's stuck in recovery?
As always, thanks thanks thanks. And thanks.
I made a post asking bftb0 to lend you a hand.
http://forum.xda-developers.com/showpost.php?p=15386610&postcount=33
Are you able to get it into fastboot mode? To do so, the phone needs to be completely off first...pulling the battery if needed. From there, first hold down the green send/call button then press and hold the red power/end button at the same time. Holding both should bring you to the fastboot screen which has three small skateboard andy's at the bottom and the word FASTBOOT highlighted in red. If you get there, post what the top two green lines say. Post #4 in the thread phone_cell gave shows an example of what you'll see. I would also try and follow bftb0's directions in post #5 about using the "Official" RUU utility to install usb drivers but make sure to stop before actually flashing anything to the phone. After that, download the fastboot tool and then with the phone connected through usb, see if the command "fastboot devices" lists your device ID.
Getting that far is promising and you can proceed with bftb0's directions in that thread to flash with HBOOT, load a recovery, hopefully eventually get a custom ROM flashed.
Hey MongooseHelix (great nick). Thanks for your reply.
No, the phone does not boot into fastboot, or anything else. There's plenty of resources here for all the different methods for booting and such. I've read hundreds of threads and pages. I've tried them all (and to success on other phones). It only gives me the recovery-stuck-ness.
The more I think about it, the more I think it has something to do with me not having this certain phone installed on my computer prior to receiving it. ? What would other people do to remedy something like that..? Find a working model to get the drivers working? Hmmm. Thanks and thanks again folks.
If you haven't already, how about installing the android-sdk(try the exe if on windows):
http://developer.android.com/sdk/index.html
Then run the SDK Manager.exe from the SDK directory. I'd download the latest SDK tools, SDK platform-tools, and the USB driver for Windows. Make sure to add the tools and platform-tools directories to your path...instructions at the end of Step 5:
http://developer.android.com/sdk/installing.html#sdkContents
With the phone on and connected through usb, see if running "adb devices" from the command prompt recognizes the Eris.
Yes, I had the android-sdk installed prior to receiving this phone. I did run it and update everything within it (per everything I researched online). But, the phone still doesn't show up via "adb devices". I feel like because the phone is stuck in recovery, it's not letting the computer do anything hardware-wise with it. ? Not sure.
Not sure what else to suggest. Without access to recovery, fastboot, or hboot along with not being able to connect through a comp, it unfortunately sounds like it might be hard-bricked. I'm certainly no expert at reviving an Eris so someone may know a way to to fix things...maybe bftb0 will come work his magic. Good luck and if I find or think of anything else I'll let you know.
The red triangle screen is indeed a splash screen for the stock recovery.
The next question is whether you are able to proceed beyond the "splash screen" and attempt to perform a "factory reset" procedure using the stock recovery menus.
There are two ways you get past the stock recovery splash screen, and it depends on which version of the stock recovery is installed on your phone have.
(1) press & hold Vol-Up+End simultaneously (with the "red triangle" splash screen showing)
or
(2) press the Home(soft-key)+End simultaneously (with the "red triangle" splash screen showing)
Do either of those cause the <2e> recovery menu to appear on the screen? If so, perform a "factory reset" using that menu, and THEN see if you can get alternate startup modes to occur (after powering off the phone before each trial):
End (only) => Does anything boot now?
VolDown+End => HBOOT
Send+End => FASTBOOT
VolUp+End => Recovery boot (red triangle screen again) **only works if HBOOT > 1.49.xxxx
Please do not say "I tried everything" in your reply. It is extremely non-specific, and conveys no information about what you actually attempted.
bftb0
Many thanks for the reply. !
With the recovery splash screen showing, upon holding "Volume Up + End (power)" I get = E:Can't open /cache/recovery/command Now, I am able to clear that message by pressing "Volume Up + End" again, however it just goes back to the recovery splash screen.
I held down Home (on the glass) + End (power) and nothing happened.
?? Any suggestions ?
Also... my reference to "tried them all" in my earlier post meant that I have tried just about every combination of simultaneous key pressing upon powering up (booting from no power) the phone. I am also familiar with the recovery menus on other phones - I have not seen it show up on this one (per my most recent post as well).
cjslugbug said:
I get = E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
That message is quite normal. However, what usually happens is that the (stock) recovery <2e> menus appear immediately after that message.
I guess this suggests that there is something wrong with the phone (hardware) or the recovery.
I'll give it some thought (check this thread every so often), but I don't see an immediate way out of your situation.
bftb0
Well, I certainly appreciate the replies. Thanks!
Does
VolDown+Send+End
do anything interesting - either from a phone off condition, or when the "can't open /cache/recovery/command" message is on the screen?
Was there a (properly formatted) SD card in the phone when you performed all the prior button-pressing experiments?
Booted with "Volume Down + Send + End" = same, straight to recovery splash screen.
I then "Volume Up + End" to get "e:can't open /cache...." and tried "Volume Down + Send + End" = no changes.
I have an sd card in it that I used to root a MyTouchSlide recently. It has ClockworkMod recovery on it (update.zip). I have done every procedure I've mentioned in this thread with and without the sd card in the phone.
I just reread the whole thread.
I understand that you tried all the standard button-press-startup methods, and the only thing you can get to work (partially) is the first part of the standard recovery boot. What you didn't say explicitly is, what exactly happens when the standard button-press operations fail:
- nothing at all (screen stays black, not a single LED blips, etc)? or,
- every start sequence results in the recovery splash screen? or,
- the three skating droids appear but the screen freezes that way? or,
- other?
Here is what you are up against:
The standard recovery does not start up an "adbd" daemon, so worrying about drivers is not likely to get you anywhere: under normal circumstances, "adb" simply doesn't work with a standard recovery.
There are two exceptions to this:
(1) The (leaked) HTC "Root ROM" does start an adbd daemon (but "adb shell" won't work)
(2) The Leak-V2 recovery had a race condition that allowed less than 20% of the folks who tried it to get an adbd daemon to persist. (Search for "tereg" root). It's a huge long shot.
Whether either of these apply to you is indeterminate, as we know neither the bootloader version that is on your phone, nor the version ofthe (damaged?) recovery on the phone.
One more question, and then some straws to grasp at:
- when you plug the phone into the charger, do you see the amber/green LED light up?
- repeat every one of the "standard-button-press" sequences, but make sure that before each start sequence, you pull the battery, press all buttons, wait 10 secs, and then reinsert the battery. Long shot, but what have you got to lose?
bftb0
- what exactly happens when the standard button-press operations fail:
The three skating droids appear (for a few seconds, as per a normal-type boot is beginning) but then the screen freezes to the recovery splash screen.
- when you plug the phone into the charger, do you see the amber/green LED light up?
Yes, I see the amber/green light. The light seems to operate as if it is charging normally.
I will try your 10 + second-battery-pull-button-combinations method here in a while.
Really appreciate the thoughts/help on the matter. !!!
Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Jason Farnon said:
Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Click to expand...
Click to collapse
1. you obviously flashed a kernel WITH CWM via Odin.
2. Rom Manager should not be used.
Flash a rooted stock ROM via ODIN.
read around in the stickies of the i777 forum, and get acquainted with things.
Boot into CWM correctly, and go about flashing whatever you want knowing what you just learned by reading the correct stuff.
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Actually the problem is most likely the fact that he is probably using an old version of cwm where the home button selects stuff. And rom manager.
Sent from team Pirate! Using Tapatalk 2
karate104 said:
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Click to expand...
Click to collapse
Thanks, that did it. I'd actually read the stickies, I just didn't think I could get into download mode because the phone was stuck in that auto-reboot loop.
For anyone else stuck in that loop cwm recovery loop, the download mode entry method (press both volume keys and insert usb) needs to be timed just so, since you usually perform the sequence when the phone is powered down (in stable way) but in this situation you only have a moment before it restarts. After powering down, just as it restarts automatically you can see the capacitative buttons blink for an instant, and that's when I started the sequence. Took me about half a dozen times but I eventually caught it. Am I the only one struggling with how hard these captchas are getting over the years? there's probably a sticky for that too I guess nvm.
If I'm not mistaken you can get into download mode without having a battery plugged in, so no need for trying to time it. Just hold volume buttons and plug in USB. For future reference; glad you got it worked out. Make sure to read the second guide thoroughly so you know how to safely flash stuff, and hit my thanks button if i helped you out.
Sent from my SGH-I777
I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
- Tried Kies and the phone was not recognized in either DL mode or boot loop. Was hopeful Kies could reinstate the firmware.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
tone_la said:
I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
Click to expand...
Click to collapse
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
dandrumheller said:
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
tone_la said:
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
Click to expand...
Click to collapse
Unplug the USB when you do that
Sent from my Galaxy Nexus
Stop using brick. It turns on it is not a brick
Sent from my GS4 running CM11 Kandy Kane
Pirateghost said:
Unplug the USB when you do that
Click to expand...
Click to collapse
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
Click to expand...
Click to collapse
I've tried very hard to not "waste" anyone's time by doing my research, searching, and thinking; BEFORE posting. My question above is not so much "how" to clean the port, but "does this symptom I'm experiencing sound like a 'bad port' issue?". Believe me, I've done tons of searching to try to solve this problem before posting so that I can be worthy of receiving assistance.
And to the guy who says, "don't use the term brick". Sorry I said "Apparent brick"; just looking for some neighborly help to get my phone working again. At any rate, I very much appreciate any advice to help me get this fixed.
Trying hard to keep the forum clean and think for myself when possible!
dandrumheller said:
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
tone_la said:
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
Click to expand...
Click to collapse
I should elaborate a little for safety's sake - probably a no brainer, but in case - TAKE YOUR BATTERY OUT BEFORE CLEANING THE PORT. Don't know if it matters or not, but I wouldn't want you to short stuff during cleaning - rubbing alcohol IS part water.
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Red_81 said:
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Well, I cleaned the heck out of the USB port with rubbing alcohol and a toothbrush, followed by a thorough drying with compressed air. Yes, battery removed during the process; thanks for that! Unfortunately, same exact symptom. Only goes into DL mode and boot loop.
I'll now try your portable adb suggestion and see if I can get a connection.
Does anyone else have any thoughts on what may have gone wrong and/or anything I can flash via ODIN to fix the issue? Many thanks!
Installed your portable adb and followed your instructions. Ran the recovery_mode batch file and adb initialized (daemon not running, starting daemon...) followed by red text "Waiting for your device to be detected". I already installed the Android SDK yesterday and the following modules are installed: Android SDK Tools, Android SDK Platform-tools, and Google USB Driver
Powered on the phone and after a few seconds the "Rethink Possible" logo showed up and shortly thereafter, I heard the computer beep indicating it connected with the phone. Win7 device manager shows "SAMSUNG Mobile USB Modem" under the Modems category.
However, the portable ADB continues to show "Waiting for your device to be detected" and the boot loop continues. Did the same thing in DL mode, same result.
I reinstalled the Samsung I777 driver from Samsung's site. Going to reboot my PC now to see if that makes a difference.
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
tone_la said:
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
Click to expand...
Click to collapse
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
dandrumheller said:
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Click to expand...
Click to collapse
Why would it work better in Linux? I'm willing to try this, but fairly unfamiliar with Linux.
Phalanx7621 said:
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
Click to expand...
Click to collapse
I used the Samsung drivers. Kinda leary of these drivers from softpedia. They download as SETUP.EXE and seem like inauthentic/spyware.
After many many hours of frustration and dead ends, I've finally recovered my phone! YAYYYYY!!!!!
Here's how I got it done...
- No matter what I flashed, I kept getting the boot loop. This was really throwing me for a "loop" when I thought I was flashing standard original Sammy full ROM with ODIN; yet that wasn't enough to recover the phone.
- Something was missing with the boot process, so I started looking for CWM that I could flash via ODIN. Most sites had the zip CWM file, but only a few had the TAR file. Finding a valid file proved more difficult than I thought with all the download sites that went offline for legal reasons. But I did find one!
http://www.mediafire.com/?bjhx33o4viz8tza
The above link is for file name: SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar
- Once I installed the above via ODIN, all of a sudden ADB recognized the phone and I was able to run: ADB REBOOT RECOVERY
It's very possible that the 3-button recovery may have worked too, but when I saw the device show up on ADB, I didn't want to take the chance.
- The device then rebooted and entered RECOVERY mode! FINALLY!!!!
- I then did a factory reset / wipe and rebooted the phone. It came up just fine, NO MORE BOOT LOOP!
Thanks to those who replied to this thread. The responses helped me think hard about what was going wrong and ultimately I dug up a solution.
alright guys, so here's the story. just yesterday i bought a brand new lg v10, got it home and the first thing i did was root the device and used ADB to load TWRP following the instructions here on SDA to a T for the ROOT/RECOVERY setup. and it worked. all was fine and dandy, the first time i booted into TWRP via ADB after root i got in, flashed a debloated ROM + xposed and again, everything went fine.. loaded into the OS of the new ROM, went through setup, turned on USB debugging, clicked always allow this computer, installed xposed app yadayadayada. I then, using ADB again, loaded into TWRP. i created a backup there just in case something went wrong with the changes i was about to make and once the backup was complete i loaded back in to the OS. at this point i thought i had done everything right and was confident that if i made system changes that didn't work out i could just flash the phone with TWRP from the backup i made. right? WRONG! ...apparently... so anyways, i made my first change, which was to use a NONROOT app called texdroider or whatever to change my DPI (as i have done with a couple phones previously without much issue) but i didn't take into account that stupid second screen... making the DPI changes system wide, as i'm sure those of you that know this phone are aware, causes the systemUI to crash with an error.. making the OS unusable.. so i tried to load into TWRP by holding the volume down and power button.. but instead it just booted me to the factory recovery.. not TWRP... the phone is unusable within the OS, i can't get the phone to connect to adb to boot into twrp as i had previously, i can't seem to get the phone into download mode, and i can't boot to TWRP and the OS is junk at this point.. but it DOES say on the "LG" screen that the bootloader is unlocked so i'm really hoping i'm not completely out of luck.. but i am not sure what to do at this point. does anyone here know of anything i can try to get into a custom recovery at this point? if i could get into TWRP my SD card in the phone has a backup, the original image, not to mention i could pull the SD card and add anything i need via my pc and then boot back to twrp etc etc and i would have no issue fixing the phone... i really don't understand what i did wrong or why i can't boot to my custom recovery but i'm at a loss.. i'm just looking for a way to force the phone into a custom recovery... or restore the original factory image.. if you have any advice at all i would really appreciate it.
Thanks for reading
**UPDATE** this may or may not make things much easier... but I got download mode working!! so at least there's that, still no custom recovery and i'm currently looking for a KDZ or TOT file to flash via lg flash tool... hopefully that makes things easier..
When you say you got to the factory recovery, what was that, an Android on its side or something asking you to factory reset your device? If it was the factory reset screen, if you select yes and then yes, it will take you to TWRP if you have it installed. If you don't it will factory reset your device.
ngoblirsch said:
**UPDATE** this may or may not make things much easier... but I got download mode working!! so at least there's that, still no custom recovery and i'm currently looking for a KDZ or TOT file to flash via lg flash tool... hopefully that makes things easier..
Click to expand...
Click to collapse
To boot into recovery from power off, you hold volume down & power. When you see the LG logo release and press power while continuing to hold volume down. Then as said above, it come up as a factory reset, select yes each time, and it should boot into twrp, providing you installed it correctly.
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
When you say you got to the factory recovery, what was that, an Android on its side or something asking you to factory reset your device? If it was the factory reset screen, if you select yes and then yes, it will take you to TWRP if you have it installed. If you don't it will factory reset your device.
Click to expand...
Click to collapse
it was a screen asking me to do a factory reset, i click yes, it asks to confirm, i click yes again and then it "successfully" factory resets my phone... it shows the android factory reset symbol that its resetting, then says that its "optimizing apps" and goes through that whole process.. but when it finally loads the "welcome" screen (so i know for a fact that some sort reset has taken place) i get the same "systemui has crashed" error and the OS is unusable and won't connect to my computer.. idk why i can't access TWRP.. i booted to it 3 times before this happened, though never by the hardware buttons on the phone.. everytime i booted to TWRP i had used ADB to boot to TWRP.. what makes me the most sad is that i have a nandroid backup on my SD card... but i can't flash it without recovery.. which i can't install on the phone without getting into the OS..
is there any way to install TWRP or even boot to a temporary TWRP so that i can do so? if i can flash my nandroid i'm saved.. if i can get into a custom recovery i'm saved.. if i can find a .kdz file to flash, i'm saved... if i can get my phone to be recognized by my computer/adb i'm saved.... there simply has to be a way to unbrick this phone...
ZDeuce2 said:
To boot into recovery from power off, you hold volume down & power. When you see the LG logo release and press power while continuing to hold volume down. Then as said above, it come up as a factory reset, select yes each time, and it should boot into twrp, providing you installed it correctly.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
well i seem to have somehow NOT installed TWRP correctly because it just proceeds to factory reset my phone.. which for some odd reason doesn't reset the DPI... leaving me stranded... is there any way to get ADB to see my device in its present state? my computer makes the device recognition noise when i enter download mode and i can see it in device manager but not my computer or ADB
I've had this phone just over 2 months but I'm not positive, is download mode the same as the bootloader on this device? If so, fastboot commands should work, and you can flash TWRP again, or do 'fastboot boot TWRP_filename' and it will boot TWRP temporarily.
Oh, and the factory reset just wipes your data, but otherwise doesn't restore your system to factory state. That's why your dpi change remained.
YrrchSebor said:
I've had this phone just over 2 months but I'm not positive, is download mode the same as the bootloader on this device? If so, fastboot commands should work, and you can flash TWRP again, or do 'fastboot boot TWRP_filename' and it will boot TWRP temporarily.
Oh, and the factory reset just wipes your data, but otherwise doesn't restore your system to factory state. That's why your dpi change remained.
Click to expand...
Click to collapse
dude.. then what good is a factory reset?!? like seriously... and yeah, i tried that but i can't get adb to connect in download mode.. the device doesn't show up when I type "adb devices" like it did when i first rooted it. ... and i thought i followed the instructions exactly as it was laid out from this link.
http://forum.xda-developers.com/tmobile-lg-v10/general/guide-how-to-root-lg-v10-easy-t3274699
i think somewhere in there i must have missed something and ended up only booting into twrp temporarily.. which is certainly possible since i never boot to twrp during that initial process from the hardware keys or soft keys.. always through adb.. the phone was already plugged in.. typing the command was a couple keys away..
is there anyway to get TWRP on to the phone now? or am i screwed :'(
Well, it is a factory restore for the average user, because the average person isn't modifying their system. But no, I'm sure you're not screwed. If you're in the bootloader you can't use adb, you're already past that step, so you can skip to the fastboot part. What happens when you type fastboot devices? If the phone shows up then you can either fastboot flash or boot TWRP..
YrrchSebor said:
Well, it is a factory restore for the average user, because the average person isn't modifying their system. But no, I'm sure you're not screwed. If you're in the bootloader you can't use adb, you're already past that step, so you can skip to the fastboot part. What happens when you type fastboot devices? If the phone shows up then you can either fastboot flash or boot TWRP..
Click to expand...
Click to collapse
from what screen should i be attempting this? hold volume up with phone off and plug in to computer to enter download mode? should i try it at the factory reset screen (volume down plus power)? those are the only two screens i seem to have access to.. in download mode my pc/adb just doesn't recognize the phone.. it doesn't show up as a proper device like it did before this whole thing and in that factory reset mode i get nothing.. the download mode seems like its built for LG and runs from different drivers because in device manager it shows up with an error code that it couldn't start the device (this was not the case when i was using adb to unlock the bootloader and then using the bootloader to boot to TWRP..) what am i missing?
and hey, thank you so very much for taking time out of your day to help me. I really do appreciate it.
ngoblirsch said:
from what screen should i be attempting this? hold volume up with phone off and plug in to computer to enter download mode? should i try it at the factory reset screen (volume down plus power)? those are the only two screens i seem to have access to.. in download mode my pc/adb just doesn't recognize the phone.. it doesn't show up as a proper device like it did before this whole thing and in that factory reset mode i get nothing.. the download mode seems like its built for LG and runs from different drivers because in device manager it shows up with an error code that it couldn't start the device (this was not the case when i was using adb to unlock the bootloader and then using the bootloader to boot to TWRP..) what am i missing?
and hey, thank you so very much for taking time out of your day to help me. I really do appreciate it.
Click to expand...
Click to collapse
No problem buddy, and sorry for the confusion. You want to be on the bootloader screen, so here is what you can do: turn the phone off(or remove the battery if you have to, and put it back in), plug the usb cable into the computer only(not phone), hold volume down on phone, plug the usb cable into the phone. That should get you into the bootloader, and then you should be able to fastboot flash or fastboot boot TWRP.
Waiting for a resolution to this thread!
I'm pulling for you from the cheering section. (otherwise known as afraid to do it myself section!)
I'm pretty sure others have come through this exact situation unharmed (I've pretty much read every thread here.) so it's only a matter of time before you get this figured out.
Here's hoping it's sooner than later.
Sorry I can't offer more besides encouragement!
Sent from my pretty nifty brand new LG V10
ngoblirsch said:
from what screen should i be attempting this? hold volume up with phone off and plug in to computer to enter download mode? should i try it at the factory reset screen (volume down plus power)? those are the only two screens i seem to have access to.. in download mode my pc/adb just doesn't recognize the phone.. it doesn't show up as a proper device like it did before this whole thing and in that factory reset mode i get nothing.. the download mode seems like its built for LG and runs from different drivers because in device manager it shows up with an error code that it couldn't start the device (this was not the case when i was using adb to unlock the bootloader and then using the bootloader to boot to TWRP..) what am i missing?
and hey, thank you so very much for taking time out of your day to help me. I really do appreciate it.
Click to expand...
Click to collapse
Hold volume down and plug the cable in, already have completed in terminal.....
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
No problem buddy, and sorry for the confusion. You want to be on the bootloader screen, so here is what you can do: turn the phone off(or remove the battery if you have to, and put it back in), plug the usb cable into the computer only(not phone), hold volume down on phone, plug the usb cable into the phone. That should get you into the bootloader, and then you should be able to fastboot flash or fastboot boot TWRP.
Click to expand...
Click to collapse
planetbeen said:
Waiting for a resolution to this thread!
I'm pulling for you from the cheering section. (otherwise known as afraid to do it myself section!)
I'm pretty sure others have come through this exact situation unharmed (I've pretty much read every thread here.) so it's only a matter of time before you get this figured out.
Here's hoping it's sooner than later.
Sorry I can't offer more besides encouragement!
Sent from my pretty nifty brand new LG V10
Click to expand...
Click to collapse
ZDeuce2 said:
Hold volume down and plug the cable in, already have completed in terminal.....
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
@ngoblirsch Along with the information provided in these suggestions and what you have said, you need to reinstall your LG/fastboot drivers on your PC while in fastboot mode
YrrchSebor said:
No problem buddy, and sorry for the confusion. You want to be on the bootloader screen, so here is what you can do: turn the phone off(or remove the battery if you have to, and put it back in), plug the usb cable into the computer only(not phone), hold volume down on phone, plug the usb cable into the phone. That should get you into the bootloader, and then you should be able to fastboot flash or fastboot boot TWRP.
Click to expand...
Click to collapse
OH DEAR GOD THANK YOU!!!!
I spent all damn day yesterday trying to figure out how to get to the bootloader on this phone.. everything i read online said to hold volume down PLUS power while plugging it in and it was NOT working lmao. dude, thank you so much. after i read that comment here it took me about 30 seconds to connect to adb and boot to TWRP. This thread can be listed as RESOLVED!
Thanks again!! can't wait to start tweaking this awesome phone!
planetbeen said:
Waiting for a resolution to this thread!
I'm pulling for you from the cheering section. (otherwise known as afraid to do it myself section!)
I'm pretty sure others have come through this exact situation unharmed (I've pretty much read every thread here.) so it's only a matter of time before you get this figured out.
Here's hoping it's sooner than later.
Sorry I can't offer more besides encouragement!
Sent from my pretty nifty brand new LG V10
Click to expand...
Click to collapse
Well I appreciate the encouragement, it sure seems to have helped! Issue has been resolved. ended up that i just didn't know the hardware key combination to get to the bootloader/fastboot mode without being already connected to adb. nothing that i could find online said to hold volume down while plugging it in to a computer. as soon as i was able to do so i connected to adb and it was a breeze from there; I am now back with an OS AND a customer recovery properly installed on the device!! I will be hanging around these forums for as long as i have this phone so i'm sure i'll bump into you guys! absolutely love the community here on XDA, you guys are freaking awesome!!
ngoblirsch said:
OH DEAR GOD THANK YOU!!!!
I spent all damn day yesterday trying to figure out how to get to the bootloader on this phone.. everything i read online said to hold volume down PLUS power while plugging it in and it was NOT working lmao. dude, thank you so much. after i read that comment here it took me about 30 seconds to connect to adb and boot to TWRP. This thread can be listed as RESOLVED!
Thanks again!! can't wait to start tweaking this awesome phone!
Click to expand...
Click to collapse
Glad you got it fixed, and welcome to the V10 device and forums!