Database Users

[Q] Need help with semi/soft brick!

So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix

First of all, there's no such thing as semi brick, there's brick or not. Try installing your Rom again..

Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App

iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
dude, he cant back up if he cant access the homescreen. neither can he use rom manager..
cant use the hardware buttons to get into dl or recovery either... read op guys...
2010ngojo said:
[Q] Need help with semi/soft brick!
So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix
Click to expand...
Click to collapse
Do this bro... just tested it myself, works fine...
get adb installed on your computer, should already have it if your rooting but if not get it, youll find it in the stickied thread for informative links in the development section.
get a cmd prompt open on your computer and type in
>adb devices
let it start up deamon and it will tell you device not found, its ok.
now type and have ready...
>adb reboot recovery (do NOT press enter yet)
start your phone like normal. before its even finished with the boot up tmobile animation and the galaxy s (but after the plain vibrant text/picture) logo press enter. if it says error: device not found then wait all the way till galaxy s only you did it too early...
screen will go black and reboot into standard recovery... hope to goodness you had a working clockwork recovery installed and nandroid ready for this next part...
go down using your volume keys and select reinstall packages using the power key
now in clockwork recovery go down to nandroid
now go to restore
go to your earliest back up and restore it.
there you go.
I would start fresh get odin set up and reinstall the original rom at this point as something may still be corrupted, reroot, install latest clockworkmod, latest vibrant 9 rom (im using and see no bugs and runs better then the vibrant 6 rom i had) and DONT install the lag fix until the newest "TRUE" lag fix comes out with the new file system and kernel that JAC is working on and has almost ready.
good luck and pm me if any of these steps need further explanation.

Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App

iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
iwillkillyou said:
Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
hes just stated man that he cant even get into recovery, my guess is hes locked out using the volume up/down keys like many new phones are (which btw is a known defect, spend 10min on the phone with tmobile doing thier trouble shooting to show them it doesnt work and they send you a replacement..) sooooo I gave him a way to get into recovery without the buttons and not having to wait till he gets to a black screen where possibly its frozen and he cant use adb commands.
I was just making mention to you also that he cant even back stuff up NOW (hopefully he already archived all his apps and data) and hes better off starting fresh since hes getting problems using his current rom/lagfix....

Thanks for the quick reply p()()pypants, but i will have to try your method later. It's late and I have class (college) tomorrow, but i will post my results soon. Thank you again.
Edit 1:
Btw, is there a way to back up my current rom? Like the way rom manager back up roms? I know my current rom works before so that's why I want to back it up.
Edit 2:
Actually i did not use adb to root my phone, just used the one click method. So can you please give me more detailed instructions on how to install/use adb?

Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.

2010ngojo said:
Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.
Click to expand...
Click to collapse
Do you have the right drivers installed? You can check here: http://forum.xda-developers.com/showthread.php?t=728929
Another very stupid question, just to cover all bases - your phone is plugged into the computer, correct? When you install the new drivers, try plugging the phone into a different USB port on the computer than you've been using, so it will hopefully pick up the new drivers without much extra effort.
If that doesn't help, just keep trying the command while the phone boots up. Maybe you'll get lucky and it will work. Sorry I don't have any real solution for you :\

I'm fairly sure I have the right drivers, otherwise I wouldn't be able to root in the first place. Yes, the phone is plugged in also. I'll try a different USB port and see what happens...
Update: Trying different USB ports does not help.

ClockWork Boot Loop

i am reading all that i can find and try, but cant seem to get this Transformer Tf101 out of boot loop, cant believe i never heard or saw that clockwork would do this, can someone point me in the direction i need to be in to fix this awesome tablet. Thanks

mikehe said:
i am reading all that i can find and try, but cant seem to get this Transformer Tf101 out of boot loop, cant believe i never heard or saw that clockwork would do this, can someone point me in the direction i need to be in to fix this awesome tablet. Thanks
Click to expand...
Click to collapse
PERI should work (http://forum.xda-developers.com/showthread.php?t=1681155)

JoinTheRealms said:
PERI should work (http://forum.xda-developers.com/showthread.php?t=1681155)
Click to expand...
Click to collapse
tried that but i cant seem to get the drivers for tablet loaded its in clock work recovery 5.8.3.4 screen right now, let me try again

trying to get win 7 (64) see this thing is a ***** cant seem to get it to see drivers and i cant find adb package if there is one

Try the recovery from 1 click root app, working fine think its rogue 1.3
Sent from my HTC One X using xda premium

I have the same problem with my tf101 and this recovery, have tried flashing other recoveries and changing kernels etc but whilst clockwork says its flashing fine it doesnt seem to get it out of the bootloop and just always loops back into the same 5.8.3.4 recovery. adb doesnt seem to be working either as it is coming up just as 'transformer' in other devices in the device manager and cant find any drivers or wont let me install the adb ones for it. Not sure what to do was just swapping recoveries as I needed to flash an update off my sdcard and this recovery didnt seem to have that option.
Any luck fixing it? Peri or one click root dont seem to be working because of the missing drivers I am assuming?

Whoops silly me forgot to do a cold boot into the OS that fixed it....
Sent from my Transformer TF101 using xda app-developers app

ok if i power off tablet hold volume down then when it starts into recovery, if i dont do anything it will show a screen that gives 2 options "wipe data" and "android" if i just wait a few seconds it will boot up into cynagenmod rom and tablets works, but anytime i try to use boot into recovery it throws it back into CWR and then the loop starts again. how do i get this CWR off of tablet.

mikehe said:
ok if i power off tablet hold volume down then when it starts into recovery, if i dont do anything it will show a screen that gives 2 options "wipe data" and "android" if i just wait a few seconds it will boot up into cynagenmod rom and tablets works, but anytime i try to use boot into recovery it throws it back into CWR and then the loop starts again. how do i get this CWR off of tablet.
Click to expand...
Click to collapse
You need to get rid of that "bad" recovery. Go to the dev section, get one of the recovery there, your choice doesn't matter.
boot into recovery and flash the new recovery.
When done don't use reboot option in the recovery.
Use the Vol down plus power button and let it get to the 2 options of wipe data or cold boot linux (just like you did earlier).
Once it boot to your OS use terminal (free in Play Store).
Open terminal and type in the following
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
*press ENTER after each line.

what do u mean dev section and recovery, i loaded the asus recovery install.apk loaded that i get into terminal but i dont know cmd syntax at all so in the second line of ur instruction what does the "|" represent
if i did it right i get message that says cannot open for write: no such file or directory

Dev = Development
Go to the development section and get either Roach's version of CWM, TeamWin recovery or Team Rouge recovery.
That "|" is a verticle bar.
If you're keyboard don't have it, get Hacker's keyboard.

ok i flashed rogue recovery and will try the terminal commands again

ok now i get 5+0 records in
5+0 records out
5 bytes transfered, is that a good sign

Thank You baseballfanz for you help, shes back in action

That's good to gear.

[HELP!] Stuck in recovery

This was my very first android device and I loved it until I tried rooting it. I did some research and got going. Upon getting into clockwork I flashed my system I thought this was what I was supposed to do...I was very...very wrong. I've been trying to follow this video <not allowed to post it> It's called "Tutorials:Root & Unlock Nexus7 Using Mac"
My problem is now, I'm stuck at the recovery screen and no matter what I do I cannot get out. It won't even show up in adb anymore. I'm really angry at myself right now and I really need help. Please help me before I smash my hands with the Nexus 7.

You can get into adb by using the boot loader. Reboot the device by holding down all 3 buttons and it will go into boot loader
Sent from my Nexus 7 using Tapatalk 2

re;
redundant409 said:
You can get into adb by using the boot loader. Reboot the device by holding down all 3 buttons and it will go into boot loader
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Once I'm in here though, how can I get back to a Android OS...
No matter what I do..it's recovery. I need help man!
--------
UPDATE: Made it into Clockwork at least. Upon doing so I tried doing a factory reset. Still just recovery. God I am such an idiot! I feel like this isn't even fixable and I just wasted all $250 on this device.
UPDATE #2: I fixed it!!! I'm so proud of myself. I kind of hacked it up to do it. If anyone falls into my hole here's what I've done:
Upon entering clockwork I noticed I had the option to restore from /sdcard/update.zip
This "update" does not exist however. So, I then downloaded Cyanogenmod10 rom. I then ran:
./adb push cm-10-20120727-EXPERIMENTAL-grouper-nemith.zip /data/media
Which pushed the Cyanogenmod10 to /sdcard/
Then I opened adb shell and ran:
cd sdcard
mv cm-10-20120727-EXPERIMENTAL-grouper-nemith.zip update.zip
Then restored on clockwork from /sdcard/update.zip.
I then proceeded to do a standard reset from within ROM manager. I'm back to stock android. I'm saved! Thanks to all who have came to help but didn't know how to fix my stupid problems or have helped.

Sorry but you could still go into fastboot by holding the 3 buttons until you reach fastboot. What you probably did is to hold the button until it reboots instead of holding it a little longer to get in fastboot
Sent from my Nexus 7 using Tapatalk 2

[Q] Stuck on Google Screen- Cannot enter fastboot

Hey Guys,
I've been on android since the G1. I've troubleshooted all problems I've had since flashing cyanogenmod when he was first on xda. With this Nexus 7, however, I've kept it completely stock.
I've had it for a month and it's been great. Yesterday I downloaded a homeland torrent and watched it. Put it down, came back two hours later and it was on a black screen (it was charged when I left at least to 50% after d/l and watching the video). I pressed the power button and it wouldn't start. I finally held it down for about 30 seconds and then it went to the "Google" screen all in white letters. It stayed there. I tried holding power for 10, 20, 30, 40, 50, 60 seconds and it would just reboot to the google screen. I finally tried to enter fastboot, i was able to, and got excited at being at a functional screen that I went into "recovery" and then the google screen just popped back up. Now I can't even get into fastboot.
I've tried the nexus toolkits but they both need either abd in android or the fastboot screen. I can't get into them. I finally called google play devices support and they said they will email me within two days to replace my nexus 7. However, I'd like to get my stored images, music, videos, etc off of there at the very least (although, I'd much rather fix it and keep it).
Can you guys suggest anything?
tl;dr : Stuck on google screen, can't enter fastboot. Is there anything I can do to make it boot? Option 2: how can I at least take my (emulated /virtual) sd card data out of it?
THANKS!

You are rebooting each time you try fastboot, correct?
Sent from my Nexus 7 using Tapatalk HD

Correct. It goes black for about three seconds then back to Google screen indefinitely
Sent from my HTC VLE_U using xda app-developers app

Bump?

Wow, I see criticism every time someone mentions they're "Bricked." Now that someone finally is bricked--or at least it seems like--no one is saying anything...

What happens if you hold all 3 keys for ~30-40 seconds, it should, at that point, reboot to the bootloader.

If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2

mihahn said:
If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2
Click to expand...
Click to collapse
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD

Thanks guys!
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, holding all three, holding power and volume up, holding power and volume down doesn't work. I've tried holding power until it restarts and then doing power and volume down, up, and both. Nada.
I appreciate your input guys. I'll just return the product to google... hopefully they don't fix it without a full wipe and get ahold of my files! Yeek!

AW: [Q] Stuck on Google Screen- Cannot enter fastboot
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
But I guess the best is to replace it
Sent from my SK17i running Android 4.1.2

mihahn said:
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
Click to expand...
Click to collapse
He said he was 100% stock.
The stock recovery doesn't start up the adbd daemon. That's typical for stock recoveries.
Proves the point that even if you stay with stock on the N7, you should unlock the bootloader as soon as you get the device. Then the option of soft-booting a different recovery (fastboot boot recovery.img) would be available for rescue situations - even if the ROM stays completely stock and unrooted.

Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
When your device is on and showing Google
Press and hold the Power key till the screen goes black
Once black, press and hold the volume down key
This will take you to fastboot
Press volume key up twice then power key to select
Device should now be in recovery mode
If you wiped the OS, use Wugs Toolkit to recover from soft brick in advanced options
If you want to push files to your device and try to recover, use MSKIP's Toolkit
Hope this helps....good luck
Sent from my Nexus 7 using XDA Premium HD app

dwny said:
Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
Click to expand...
Click to collapse
Nope, not unlocked, rooted or have a custom recovery.

Can't boot, tried flashtool, not going well, help

So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?

I think it's getting a model information check fail in lg flashtool, ugh this sucks.

bova80 said:
So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?
Click to expand...
Click to collapse
LOL, i just went through the same thing. I'll be posting a fix tonight I worked out with Scott.
"There is a "back door" method. This is why they updated TWRP by the way...
Download this: https://dl.dropboxusercontent.com/u/...with cmd.zip
Extract it to desktop. open the command.bat file.
Type "adb reboot recovery" then press enter. You need to keep doing this during the factory reset.
This assumes you have drivers installed. If you have no drivers installed for recovery mode then just select generic Google Nexus ADB drivers.
You kinda have to hammer the reboot recovery command. Its all timing... To hammer it... press the up arrow in the dos prompt and that will repeat the line. then press enter.
Keep doing it until you see it reboot to twrp and you should be able to sideload or load from storage.
It may take 10 or 15 minutes to get the exact right timing so dont give up.
And of course, this is all dependent upon you having the drivers already installed."
- Scott
For timing, you'll need to wait right when TWRP starts writing the script and start hammering it out. Timing is everything so when you see the TWRP screen starting hitting the up cursor and enter. It should load recovery. Don't bother using the tool, it won't work as it thinks your device is a D802 and won't be compatible with the dll. This will get you back to normal and from here you can just wipe and reinstall the rom again fresh with out losing media/data on the your drive.

I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated

MkV05 said:
I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated
Click to expand...
Click to collapse
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.

SamsungGalaxyStig said:
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.
Click to expand...
Click to collapse
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?

ccmbr002 said:
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?
Click to expand...
Click to collapse
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip

so I got it right when it said teamwin to reboot but everytime it reboot it tried to run the script and would never actually go into twrp. att is sending me a new phone but I'm worried when I send this one back they'll get me for being rooted.

SamsungGalaxyStig said:
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip
Click to expand...
Click to collapse
I just messaged him to double check - I don't have access to my phone for a few days (out of town) but if he hasn't responded by the time I get home I'll just go ahead and try it and post here if it works or not. Thanks again for sharing this file!

Got the file... and MANY THANKS!!! It allowed me to un-softbrick my G2 finally

this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
updating partition details
Running boot script....
Finished running bootscript,
Processing AOSP recovery commands....
----Wiping Data Partition----
Wiping data without data/media...
Done.
Removing all files under '/cache'
---- data partition wipe complete!
Done processing script file
Click to expand...
Click to collapse

bova80 said:
this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
Click to expand...
Click to collapse
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?

SamsungGalaxyStig said:
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?
Click to expand...
Click to collapse
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?

bova80 said:
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?
Click to expand...
Click to collapse
Are you constantly doing the adb recovery reboot? or once or twice?

SamsungGalaxyStig said:
Are you constantly doing the adb recovery reboot? or once or twice?
Click to expand...
Click to collapse
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?

bova80 said:
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?
Click to expand...
Click to collapse
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.

SamsungGalaxyStig said:
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.
Click to expand...
Click to collapse
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?

bova80 said:
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?
Click to expand...
Click to collapse
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?

SamsungGalaxyStig said:
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?
Click to expand...
Click to collapse
on a pc. when i go under device manager I think it says something like lg modem, I'll know for sure when I get home.

omg it finally worked! thanks, I eventually just gave up with the command prompt and it went in.