I was trying to install GingerStreak. Flashed the amss and dsp1 and then got boot loops. Did a factory reset, and now I just get the buttons lit up and nothing else. Holding volume buttons & power doesn't take me to recovery. Holding camera & power doesn't take me to fastboot.
How screwed am I?
edit: now it doesn't even seem to want to turn on at all
Been there myself, and mine is fine again now, so there is still hope.
1) If it won't even power on, pull the battery. Then wait - at least a minute, more if you like...
2) reinstall the battery, being careful NOT to hit any buttons while holding the phone, then hold down the shutter button and power on to head to fastboot.
3) while in fastboot, flash the amss and dsp1 files (I use he 351 ones), and then the custom recovery of your choice, StreakMod is nice.
4) hold down the volume buttons and run a fastboot reboot, to make sure you go straight into recovery.
5) run the dell factory reset, but hold down the volume buttons to make sure you loop back into recovery when it reboots (think it does an automatic reboot, but it has been a while)
6) this time, in recovery, select option 2 and go into StreakMod, then install StreakDroid 1.9 (it is stable and this is about getting your phone back alive)
7) let it boot normally, you should end up with a happy working Streak.
After that, feel free to upgrade to GingerStreak, or head to a stock rom, or whatever, but the above should recover from most situations where you can still get to fastboot.
if steps 1 & 2 don't even get you to fastboot, then you're going to need QDL tool.
Thanks for the super guide reply. There is hope, sweet.
I plugged my Streak into a desktop it hadn't been connected too and hardware wizard popped up, so it's got something in there still.
I still can't get into Fastboot, so I've looked into QDL, however most guides reference repairtool.zip, which I can't seem to find. The Streakdroid.com link most guides use doesn't work anymore.
It is currently listed as Quallcom CDMA Technologies MSM, and has no driver installed.
Any idea where I could get repairtool?
The files I can do
here are repairtool.zip which is the full main QDL tool that takes you to 2.1 pre replease
http://www.multiupload.com/YWYDN3AEXG
and also streakflash.zip, which is a slightly older version, and doesn't flash as much - if the first one doesn't work, this one often does, it is designed to get the phone back to the point where you can repair it, rather than flash a full OS onto it
http://www.multiupload.com/1YG0JCZW7Z
As for the driver, the one I installed went something like the following (from memory)
Pull the battery, wait a minute
Instert battery, DO NOT POWER ON
hold down the volume up button, and plug in the USB lead, STILL DO NOT POWER ON
Windows should recognise a device, and try for a driver, go through the dialogues to an all devices, choose a driver, have disk, and the one you need to choose is the driver in the repairtool zip
BUT, sadly, I don't have my streak with me here, so I can't remember the exact device name that you need to choose once you navigate to that folder
as I recall, it was the model 9002, and NOT the one with modem in the name, but I could be wrong. Hopefully someone else will be able to fill in the gap
Between you and this guide
I think i should be set. Much thanks. I owe you a beer.
edit:
I just want to add a few notes on what I had to do, mainly in regards to Windows 7 64-bit. Since Streakdroid.com is currently being rebuilt and some important resources (things that lots of other post reference) are currently unavailable.
Reboot, tap F8 to get the windows start up menu, choose "Disable Driver Check"
The driver you want, even if you have an Intel chip is the ..\Driver_2.067\win64\wnet\amd64\qcser.inf
(There is one specific Intel chip that needs the driver in \IA64)
I love you guys. For three days I tried to get away from Gingerstreak (It's horriable),and I bricked my phone. You're thread was a life saver.
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.
I installed clockworkmod per instructions.
When I press the on and volume up buttons I get the appropriate message and then the system boots with the tap n tap (ugh) rom.
I never see a clockworkmod menu
What am I doing wrong?
I am having the same issue!!! I am beyond frustrated right now. I have downgraded to 1.1 and had success during one try and from now on trying to boot into Clockwork it won't let me. All it does is say booting from kernal image and then goes to the splash screen then to the box with the down arrow and continues until it goes right back to the viewsonic birds and boots to the normal rom again.
What the He!! am I doing wrong here? I have already done a factory reset with data wipe...
Instructional video
See if this helps.
How to install Clockwork mid and tnt lite - Pensacola computers
http://www.youtube.com/watch?v=27oDBi-x760
argusvision said:
See if this helps.
How to install Clockwork mid and tnt lite - Pensacola computers
http://www.youtube.com/watch?v=27oDBi-x760
Click to expand...
Click to collapse
That is exactly what I was watching and following when this happened to me. Any other ideas? I did however just return the other one after clearing the data and got another one so I am going to try and avoid doing that again.. I am going to try and tread slowly here so I can get things right....
I've had 100% success using the instructions here:
http://forum.xda-developers.com/showthread.php?t=861950
Go to the first link (Dropbox) and, if Windows, download the 2 zipped files. I will say I bought a Viewsonic G tablet back in December and I had to used the older zipped file in the DEPRECATED folder. My latest Viewsonic G tablet works with the latest files.
Unzip the 2 files, combine into one folder, plug in the USB cable, and reboot by holding the POWER button *and* the Vol- button. You should see the initial boot screen but should quickly see a black screen. Run the .bat file (nvflash_gtablet.bat). If the computer doesn't see the tablet, read the above link on how to make sure you've installed the drivers for the tablet. Once the batch file ends, your tablet will automatically reboot. I would suggest powering off the tablet before it reboots as you can install CW_Mod via NVFlash, which is what I do. Grab CW_Mod 1.1 (not 1.2). Unzip the UPDATE.ZIP file and copy RECOVERY.IMG to the folder where you combined the 2 zipped files from Dropbox. Connect your tablet to your PC via the USB cable. Reboot the tablet again by pressing the POWER button while holding the Vol- button. Same thing--i.e. initial boot screen, then a black screen. Either create a batch file or run the following command (sorry cannot remember the thread where I found this, so I take no credit for this):
nvflash.exe --bl bootloader.bin --download 9 recovery.img
This is a quick process. Once the command finishes. Unplug your USB cable from your tablet and hold down the POWER button to turn off your tablet. You can either power it back on or power it back on and check to make sure CW_Mod is installed (recommended). For this, press the POWER button while holding down the Vol+ key until you see the line of text appear in the upper left hand corner of the screen.
Again, on one of my Viewsonic G tablets, I had to use the zipped file contained in the DEPRECATED folder on the Dropbox. I can't remember what the current files did (think soft-brick).
Good luck. As I've said, I've used these steps so many times as I went through every 1.1 ROM and 1.2 ROM trying to find the one I liked and the steps were perfect. At this point, though, while in CW_Mod, I would go through the process of partitioning your system and formatting stuff.
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, I just bricked my phone while installing the CyanogenMod stable release. Chances are that the zip file i downloaded was corrupted (The filesize was much smaller, must be an internet disconnection that i did not realise) and I am unable to boot into neither download mod nor recovery mode. When holding the volume up and power button, I see the load screen with the yellow triangle (obviously), and it turns black, and the same screen appears again, except that this time, it stays that way.
I tried to see if Odin can detect the phone but because it is not in download mode, it could not detect anything even when kies was switched off. (checked task manager to make sure i killed it) However, the computer was clearly able to detect the phone. (I am using vm ware and when i connect the usb to the phone, i am prompted to choose between connecting it to windows or mac) I then tried to do it in pure windows but odin was still unable to detect the phone. I tried Heimdall to no avail as well. My jigg should arrive in 2 days but from what i seen from the [debunk] Jigg thread, I am not confident that it'll bring me into the download screen.
Is there anything that can be done without sending it for repair? Thank you
Get your battery out the phone, put it back in and hold Volume-down + Home + Powerbutton immediatly pressed, You may have to repeat this several times. When its needed to repeat it more then once let the battery every try some more time out you device.
When You get into downloadMode flash an OdinRom
Hope it will help.
Alright! Thankfully, that worked after a few tries. Tried to flash CM7 again but apparently, it does not work. Think i'll have to ask people in the relevant thread. Thanks again!
Thanks in advance for reading this and for any suggestions you might have!
I have a Archos Home Connect 35 Gen 8 device. I had it rooted on 2.4.82 firmware just fine. I wanted to update to 2.8.83 to get rid of the update notification I kept getting. I wanted to do it from a fresh clean slate as I wanted to reset my device anyway. First I used the Recovery Menu (White Menu) to restore back to default, then removed the SDE menu via the option to remove it in the SDE menu.
I then followed the guide that chrulri posted that I followed last time, but with 2.8.83 files. http://forum.xda-developers.com/showthread.php?t=930197 (Note for Archos 35's you have to hold the power button for ~6 seconds, then double tap it to get to recovery instead of holding Volume Down like on other Gen8's). I was doing this on my MacBook Air at the time. (I rooted it before from my Windows PC). I went to 'Update Firmware" on the recovery menu, then took the SDE firmware file, and copied it over USB to the drive and safely removed the drive, then hit "OK" on the device. It proceeded to do the update it seems but only took 2-3 seconds so I'm fairly sure something didn't go right as it usually takes longer. It then said press ok to Reboot so I did.
After the reboot from that, the device turns on but I get a White screen. No Archos logo or anything. Usually this white screen comes on for a few seconds, then I would get the Archos Logo even if I was booting recovery. No luck. I tried resetting the device by holding power button for 20 seconds, waiting 10 seconds and turning it on, same issue. Recovery will not work either, I tried two dozen times to try and get it to load by doing the usual ~6 seconds holding power button then double tapping and no luck.
I tried hooking the device up USB and in Windows all I get "Unknown Device" in device manager, with DeviceId of USB\Unknown. I attempted to force both Archos' ADB driver and the Universal ADB drive onto it with no success. (I'm pretty sure its my device since normally when a device shows up and its capable of ADB you will get a difference device ID in Device manager like USB\ADBDEV1 or something. On my Mac, when I plug it in, all USB devices (Multitouch pad mouse included) will lock up for ~5 seconds, then in dmesg I can see it has a error on USB device and it disabled the device.
So something weird is going on with my Home Connect for sure. Any suggestions on what to try? I'm thinking somehow the filesystem or firmware on it got screwed up during the SDE flash and it can't boot anything even the recovery now. I have a MicroSD card I can use if there's some recovery feature built into it to get it to boot from the MicroSD slot or something to do a firmware recovery.
My only other option if there is no way to try and get it back would be to try and send it back to Archos for repair simply stating it was updating firmware and this happened. (No actual modified firmware is on it now as well, and i was flashing the Archos approved SDE firmware, so they should be okay with it).
Also the battery was fully charged when doing this. It seems different that the White Screen bug the Archos 101 and others get when the battery accidentally runs too low with older firmware.
Thank you again for your replied!
If you can't get into recovery anymore, then it is over. I would suggest to RMA the device.
divx118
From all my searches through Archos forums and here that seems right.
I'm shocked there's no failsafe recovery mode for Archos. My Asus Transformer TF101 had one, where even if the firmware was screwed and you couldn't get to recovery, a special key combo would boot it up and you'd load some special recovery driver for it (Not adb something with nVidia in it, has to do with Tegra2 chipset i suppose) and upload the firmware to it and it recovered. Even iPhone's have DFU fallback mode as well for when things are totally forked and iTunes will restore the firmware.
Just an update. I did RMA the unit and Archos sent me a brand new boxed up one back. (I have an extra charger and cable now since they said not to include them ). Have my new 35 setup rooted with .83 now.
I think I figured out what happened. After I installed the SDE, before I flashed the new kernel and such, if I booted the Developer Edition option from recovery, it would get stuck at a blank white screen until I power cycled. On my old 35 I had removed the option to boot regular so it booted the Developer Edition that was rooted every time. I think when I restored the original firmware, it of course removes the Developer Edition kernel I had flashed before, but it somehow didn't set the menu back and was trying to boot Developer Edition every time, which it lacked the kernel for, and went to the white screen. Not sure if it explains recovery not working though.
To make sure it doesn't happen again i've left the options all in tact and left it so I manually have to go to recovery if I reboot the system to boot the developer kernel for root. Since the device goes weeks and months without the need to reboot since it's just an Alarm Clock really that's fine with me.