So I'm trying to return my phone back to stock, went through the whole process list in the one thread with LGFlashTool and all I ever get is it saying waiting for connection when I plug my phone in. Then when I unplug it it says unable to identity.
Also if and when I am able to flash back to stock, will that get rid of twrp too? or what can I do to do that?
Is there another way to unroot and go back to stock recovery?
Reason for all this is I had an issue with my phone and they are sending me a new one, don't want this one to show any signs of being rooted.
Can I use supersu to uninstall root?
Make sure you have the right LG utility and drivers installed... Press volume + while plugging into the pc... It should show download mode... And if you are still having issues look in the program data folder on your pc, and find the LG folder and uninstall the bcapp file... I had a major headache trying to restore my D801 and it will remove Root, and restore it back to stock... hope this helps
Sent from my LG-D801 using xda app-developers app
following the link below and every time I plug my phone in it then says waiting for connection, I don't get it.
http://g2-lg.com/how-to-unbrick-unroot-at-t-lg-g2-lg-d800-revert-to-stock-rom/
turns out I'm an idiot, was trying to change com port under modems for phone rather than Ports(com and lpt). as soon as I did it under ports it worked. lesson learned.
case closed.
Related
I notices a few users have mentioned that they're dealing with trying to restore or unbrick their Continuum after flashing incompatible kernels and other problems.
I made this backup immediately after I got root, before I did anything else, to make absolutely sure I wouldn't be SOL if anything went awry. I've made absolutely certain this works, by unzipping and flashing on my own Continuum prior to uploading. It contains the system, recovery, and kernel partitions.
This file is also helpful if you need to get back to stock for warranty purposes, in which case you can manually un-root by using your favorite file explorer (I happen to prefer ES File Explorer), grant root permissions, mount system as rw, then manually delete SuperUser from /system/apps, su from /system/bin, and busybox from /systen/xbin. I hope this helps some of you who have been stuck.
You don't need to be rooted to flash this. Simply unzip, flash the .tar.md5, and you're golden. If you end up in restore mode after flashing, you probably need to do a hard reset, but this is unlikely as I tested it by flashing this a few times after installing various programs from the Market and never had to do a hard reset.
Don't forget to put your phone in Download mode by removing the battery, then holding the vol down button while inserting the usb cable. Good luck!
http://www.mediafire.com/?a897dbakz4j7k4f
Thanks for this. I had been messing around with the phone. I was able to get it back to stock.
Kay I try to flash this and it's telling me it's an invalid image type
Never mind, I got it. Thanks
Not a problem, glad I could help!
My phone was soft-bricked. This worked like a charm. Thank you so much!
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
kingtuk1 said:
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
Click to expand...
Click to collapse
Yup, gotta wipe! At first it's so easy to forget this step. When you get to customizing your installation, you'll get to used to having to wipe it'll become second nature!
I'm so glad to hear this is coming in handy for you all! Now that you got this done, get yourself froyo, courtesy of imnuts: http://forum.xda-developers.com/showthread.php?t=1197415
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Native89 said:
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Click to expand...
Click to collapse
Read the OP from pastorbennett here: http://forum.xda-developers.com/showthread.php?t=1203597 and try the unbrick process. You can do a search for pastorbennett and trailblazer. Both have posted "recovery processes", or at least links to others that have posted recovery processes. They've saved my butt a couple of times... Except on my first phone that wouldn't go into DL or Recovery Mode. It would just flash the Samsung logo, over, and over, and over again... That happened before pastorbennett posted the unbrick info. Oh well, Verizon replaced it under the hardware warranty. Thankfully.
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Native89 said:
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Click to expand...
Click to collapse
Okay, if you can, grab a different computer (either Windows XP or Windows 7) and install the samsung drivers from this post: http://forum.xda-developers.com/show....php?t=1203597. The hint here with ANY Windows computer is to install the device drivers FIRST! (I've been a system administrator for about 20 years.) Then plug in the hardware. It usually makes the installations go MUCH smoother.
If you have to use your computer, try installing the Samsung drivers first, then plug the phone in.
zzir said:
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Click to expand...
Click to collapse
The key to odin seems to be this:
1. Start odin.
2. Click the PDA button and select the odin TAR or MD5 file. (You can only do one. Not both.)
3. Make sure the phone is not plugged into the computer.
4. Make doubly sure the phone is not plugged into the computer.
5. Put your phone into download mode. (With the phone off, hold the Volume Down button and turn the phone on.)
6. Then plug the phone into the computer.
7. Start the odin flash and you should be good to go. Also, before unplugging the phone, make sure it says either success or failed. If it doesn't say anything, or says loading (or something like that), WALK AWAY! Go get yourself a cup of coffee, a soda, a nice cup of tea... Something. I recommend waiting at least 10 minutes. If the progress bar has not moved, in that time, okay, then pull the cable and the battery and start again.
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Tarheel487 said:
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Click to expand...
Click to collapse
Did you flash the CWM Recovery in Odin? (cwm_recovery_test4_adryn.tar) Can be found here if not http://forum.xda-developers.com/showthread.php?t=1230072
is it possible to flash this with heimdall or only odin?
ntien said:
is it possible to flash this with heimdall or only odin?
Click to expand...
Click to collapse
I don't know, however, pastorbennett posted this http://forum.xda-developers.com/showpost.php?p=16600453&postcount=29. It might help? I use Linux at home to build most of this stuff, then use my wife's Windoze machine to flash. It just seemed easier.
Yes, you can use heimdall, you just need to extract this .tar and put the extracted files in the corresponding location in heimdall xD
Sent from my SCH-I400 using xda premium
yeah i saw that but in heimdall 1.3 the UI is different. i don't know where to put any of the stuff. i have the .tar but i dont know where to put the other stuff. here's a screenshot
Sorry to ask for help in this thread. But my work gave me a new razor and yesterday. It came preinstalled with jelly bean. I rooted it and installed safestrap. Went through multiple flashes with no problems. Last 1 I tried it got stuck at the fast boot. It says locked 0 battery okay. I've tried every remedy. I believe I have all the files on my computer to revert back I cannot figure out how to get ADB to recognize my command it keeps telling me that file or that system cannot be located maybe I'm working it wrong maybe I have the wrong information I really need to have this fixed by tomorrow morning if anybody can please help me either send me a private message or even call Maine just p.m. me for my number thanks sorry to take this thread hostage.
Sent from my Nexus 4 using xda premium
Well take it easy on you. For future reference, all questions and requests for help go in the q n a section. This section is for posting ROMs, kernel, mods, etc.. only. Anyway, you say that you cannot get your phone to be recognized through adb? Here are number of reasons why that might be.
1. You do not have the proper drivers installed. Install the drivers for this with the proper driver software for this phone.
2. The obvious reason is in order to use adb, your phone has to be booted on. (You can still access adb even if your stuck on boot animation) or have to be in recovery mode.
3. Make sure you have all the files in a folder you need to initiate adb commands: fastboot and a dB for example. You can get all these from downloading the SDK tool kit.
Now I do not know what remedies you have tried to restore it. But the first thing you should've done after you have installed safe strap was make a backup of your original ROM.
If all else fails, you will need to flash the jellybean stock firmware using rsd lite. Which of course requires you to have yih phone recognized by your. PC. Check to make sure it isn't your cord by hooking it up to another computer. Try swapping different cord too.
And moved...
Hello!
I think I somehow deleted a crucial file...
Okay, so my phone won't connect to my computer anymore. I am using Windows 8 so aside from Windows 8 automatically downloading the drivers on its own, I took additional steps and downloaded the drivers directly from samsungs site. I've tried using different ports, different usb cables and different computers. All that happens is a lightning bolt telling me my phone is charging.
My phone used to be rooted. When I noticed the problem, I unrooted the phone and tried restoring the phone. (I tried booting in recovery and doing it that way as well as restoring it through settings).
I've downloaded just about every app that has the word 'mount' in it to see if it will help and nothing happens.
Every time I restore my phone, the first thing that pops up is a notification saying that samsung link has stopped working. I'm on android 4.2.2
Whenever I've restored my phone in the past, I've always been successful but that was also because I was able to flash a factory ROM through odin on my computer.
When I put the phone in developer mode, it shows in the corner:
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
Root checker says I am not rooted so I'm guessing that the BINARY and STATUS is coming up as custom because I am not fully unrooted (however, I had the problem of not being able to connect via usb when I was rooted).
If you have any ideas, I will definitely try them!
Oh, one more thing. Before my phone stopped connecting to my computer, I purchased additional batteries for my phone. I say this because It had been a fairly long time before I realized that my phone wouldn't connect to my computer because I no longer used my computer to charge my phone. And I say that because when I was rooted, I used titanium backup as well as CMW and neither was able to restore my phone back to a time that the usb worked again.
Okay, I think that's it. It's a lot of details but I didn't want to waste anyone's time coming up with ideas if I had already tried one.
Thank you!
swagganation said:
Hello!
I think I somehow deleted a crucial file...
Okay, so my phone won't connect to my computer anymore. I am using Windows 8 so aside from Windows 8 automatically downloading the drivers on its own, I took additional steps and downloaded the drivers directly from samsungs site. I've tried using different ports, different usb cables and different computers. All that happens is a lightning bolt telling me my phone is charging.
My phone used to be rooted. When I noticed the problem, I unrooted the phone and tried restoring the phone. (I tried booting in recovery and doing it that way as well as restoring it through settings).
I've downloaded just about every app that has the word 'mount' in it to see if it will help and nothing happens.
Every time I restore my phone, the first thing that pops up is a notification saying that samsung link has stopped working. I'm on android 4.2.2
Whenever I've restored my phone in the past, I've always been successful but that was also because I was able to flash a factory ROM through odin on my computer.
When I put the phone in developer mode, it shows in the corner:
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
Root checker says I am not rooted so I'm guessing that the BINARY and STATUS is coming up as custom because I am not fully unrooted (however, I had the problem of not being able to connect via usb when I was rooted).
If you have any ideas, I will definitely try them!
Oh, one more thing. Before my phone stopped connecting to my computer, I purchased additional batteries for my phone. I say this because It had been a fairly long time before I realized that my phone wouldn't connect to my computer because I no longer used my computer to charge my phone. And I say that because when I was rooted, I used titanium backup as well as CMW and neither was able to restore my phone back to a time that the usb worked again.
Okay, I think that's it. It's a lot of details but I didn't want to waste anyone's time coming up with ideas if I had already tried one.
Thank you!
Click to expand...
Click to collapse
Not sure if this will work, but there's a mobile odin you can try to use.
And you can get stock ROM there.
Salil999 said:
Not sure if this will work, but there's a mobile odin you can try to use.
And you can get stock ROM there.
Click to expand...
Click to collapse
Ii'm not rooted anymore so mobile odin doesn't work
swagganation said:
Ii'm not rooted anymore so mobile odin doesn't work
Click to expand...
Click to collapse
Try and download a ROM that is pre-rooted. Maybe that will work!
Salil999 said:
Try and download a ROM that is pre-rooted. Maybe that will work!
Click to expand...
Click to collapse
Do you know how I would install a rom that's prerooted without my phone being rooted or being able to connect to a computer via usb?
swagganation said:
Do you know how I would install a rom that's prerooted without my phone being rooted or being able to connect to a computer via usb?
Click to expand...
Click to collapse
You're should have a custom recovery installed... At least that way you wouldn't need your computer. Otherwise you'd have to do it through Odin, but like you said in the OP, you can't connect to USB. Is your device rooted?
swagganation said:
Hello!
I think I somehow deleted a crucial file...
Okay, so my phone won't connect to my computer anymore. I am using Windows 8 so aside from Windows 8 automatically downloading the drivers on its own, I took additional steps and downloaded the drivers directly from samsungs site. I've tried using different ports, different usb cables and different computers. All that happens is a lightning bolt telling me my phone is charging.
My phone used to be rooted. When I noticed the problem, I unrooted the phone and tried restoring the phone. (I tried booting in recovery and doing it that way as well as restoring it through settings).
I've downloaded just about every app that has the word 'mount' in it to see if it will help and nothing happens.
Every time I restore my phone, the first thing that pops up is a notification saying that samsung link has stopped working. I'm on android 4.2.2
Whenever I've restored my phone in the past, I've always been successful but that was also because I was able to flash a factory ROM through odin on my computer.
When I put the phone in developer mode, it shows in the corner:
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
Root checker says I am not rooted so I'm guessing that the BINARY and STATUS is coming up as custom because I am not fully unrooted (however, I had the problem of not being able to connect via usb when I was rooted).
If you have any ideas, I will definitely try them!
Oh, one more thing. Before my phone stopped connecting to my computer, I purchased additional batteries for my phone. I say this because It had been a fairly long time before I realized that my phone wouldn't connect to my computer because I no longer used my computer to charge my phone. And I say that because when I was rooted, I used titanium backup as well as CMW and neither was able to restore my phone back to a time that the usb worked again.
Okay, I think that's it. It's a lot of details but I didn't want to waste anyone's time coming up with ideas if I had already tried one.
Thank you!
Click to expand...
Click to collapse
IF you can get to download mode Then jump over to this thread. Download the zipped file (from first or second post), extract the file - just to the .tar.md5 file.
While waiting for the download charger your phone to at least 50%
Also download Odin 3.x. get that here. unzip one of the Odins - I've been using 3.07
To launch Odin make sure you right-click and choose run as administrator!
Once Odin is launched go to the PDA box and select the .tar.md5 file you downloaded.
Make sure you have NOT selected re-partition. you can leave auto reboot and f.reset time checked though.
Now get into download mode - Power button + Home key + Volume down. Hold until you are asked to confirm going into download mode by selecting up volume.
Plug your phone into your computer and a com port should show in Odin3.
If it does then select start and wait till it finishes completely - it will say pass; your phone will actually reboot too.
Go through setup and there you go. new phone.
Then to root just use CF-Autoroot
My computer stopped recognizing my S4 recently, too. Odin wouldn't see it, couldn't connect it as a drive, etc. It had not been very long between when it worked and when it didn't, and I had installed a bunch of new Java stuff for (JDK7, Netbeans, Eclipse, etc). Tried the wife's S3 and same deal. So I uninstalled my Samsung drivers and Kies and booted my Win7 laptop. Reinstalled drivers, no joy. Reinstalled Kies and let it do all it's updates and that fixed the issue. Rooted, MDL, stock rom.
jejb said:
My computer stopped recognizing my S4 recently, too. Odin wouldn't see it, couldn't connect it as a drive, etc. It had not been very long between when it worked and when it didn't, and I had installed a bunch of new Java stuff for (JDK7, Netbeans, Eclipse, etc). Tried the wife's S3 and same deal. So I uninstalled my Samsung drivers and Kies and booted my Win7 laptop. Reinstalled drivers, no joy. Reinstalled Kies and let it do all it's updates and that fixed the issue. Rooted, MDL, stock rom.
Click to expand...
Click to collapse
When uninstalling old drivers make sure you go to Device manager and go to View >Sho Hidden devices and remove them too! Remove everything - all left over devices, all software and even directories for said software; Revo uninstaller works well.
Also try a brand new USB cable. Though that may not be it, I've seen that alone solve all kinds of problems! Really just a brand new cable.
If you haven't tried this already, try and make sure USB debugging is enabled?
I figured with the amount of bricked LS980s with Justins rom I've been seeing at my shop I might as well make some sort of tutorial to help some people out. Searching doesn't bring up too many threads but there are a couple and hopefully a few of the guys in those chime in. My goal is to make this visible and save many of you hours of trouble. Many thanks to Justinswidebody for building the rom. I won't post the link as most can use the search to find it just fine.
Why does the LS980 brick with Justins rom?
It updates.
I think the majority of people flash the rom and forget to take the necessary steps to prevent an update and when it does it will try to reboot into recovery and wipe the system resulting in a soft brick. Most of the time TWRP will remain, which is good, but reflashing the rom will do no good.
Right after this happens what do I do?
Imeadiately plug in you usb and adb push the stock ZVA rom onto the sdcard
use this command:
adb push nameoffile.zip /sdcard
It will take a while.
Once it finishes you need to wipe everything but internal and flash. Once done, power off and boot into download mode.
Prepare LG Flasher and correct TOT file with DLL. I may post a link later.
In my personal experience with installing justins rom it's best to start fresh with ZV7, trust me you will have less headaches. Once it finishes you're ready to redo the whole thing.
I dicked around with the phone and now I can't get into recovery?!
You have to have recovery on there.
If you can't get into download mode then your journey ends here, not sure there is a fix for that, however, you probably already have it in DL mode and getting a fail "wrong DLL" or some ****. Your phone now thinks it's a T-mobile D801. Forget the sprint files, you're gonna flash the tmobile files just to get it to boot. I actually had a customer bring me the phone and managed to flash the right combo to get it to boot but he didn't know what he did, I'll have to find them.
Now, once booted up you'll notice wifi and data will not work along with keyboard and other things thus making it impossible to download flashify and reflash recovery. The phone, in some cases, will only stay booted for 20 seconds and then reboot over and over. It's like this phone is actively tying to make your life difficult. Relax, and let the adb drivers install. Test it by opening a command prompt and write: cd/
/adb
/adb devices
Allow the rsa key. You won't have time to transfer the stock sprint ota file so we need to transfer it in recovery.
Download the simpletool flasher by OptimusRS, this will flash recovery to your phone and remember to choose d801 not ls980. Reboot into recovery. Once the adb drivers have installed you're going to adb push the stock zip back onto the sdcard like you did before. Wipe everything and flash, then power off. Once you boot into download mode it should recognize the phone as an LS980 once again and you are free to flash the correct tot and dll files.
Congrats! You did it!
How do I prevent this from happening in the future?
I've been fighting with this for a while and I think finally know how to be 100% successful in turning off the OTA, if anyone has something to add please do
Go into the app manager and find google services framework and uncheck or disable or both
Use a file manager to go up to CACHE and delete the update that will most likely be hiding in there
Go up to system/app and rename any service that looks like it would provide an update- LDdownload provider is one. I wish I had a list of all of them but I really don't know what the exact app is.
Special thanks to all the guys contributing in these threads:
http://forum.xda-developers.com/showthread.php?t=2641831
http://forum.xda-developers.com/showthread.php?t=2682926
Exactly at this point
I am exactly at this point, but not turned on usb debugging, so i don't have adb access to the phone. When I try to flash the phone with ls980 TOT it says, the device is D801 and if I try D801 KDZ file, it shows an error message "previousLoad()". I have both download mode and Recovery mode. I have tried sideloading rom on recovery, but I get an error like "E: footer invalid, E: signature invalid"
What can I do to unbrick it. I am trying desperately for the past few weeks.
Anoop S S said:
I am exactly at this point, but not turned on usb debugging, so i don't have adb access to the phone. When I try to flash the phone with ls980 TOT it says, the device is D801 and if I try D801 KDZ file, it shows an error message "previousLoad()". I have both download mode and Recovery mode. I have tried sideloading rom on recovery, but I get an error like "E: footer invalid, E: signature invalid"
What can I do to unbrick it. I am trying desperately for the past few weeks.
Click to expand...
Click to collapse
Honestly, this kind of brick is a *****. I had a customer bring in one that he actually used Flashtool to put on the original t-mobile dll and tot file, and adb does not work in order to get recovery on. Sucks.
Not many people have experience with this stuff and flashtool is a pain when this happens
2strokenut said:
Honestly, this kind of brick is a *****. I had a customer bring in one that he actually used Flashtool to put on the original t-mobile dll and tot file, and adb does not work in order to get recovery on. Sucks.
Not many people have experience with this stuff and flashtool is a pain when this happens
Click to expand...
Click to collapse
Lol I'm having this issue with one of my customers and it fails. I unlock these things and pass them on but I ALWAYS disable the Google Play Services firmware update in order to avoid this and clearly warn them NOT to factory reset.
This one guy got his elsewhere and the guy gave him no warning on the update. So he contacted me and his is worse than my first experience with the T-Mobile rom OTA brick. Seems like his seller didn't use AutoRec which is more reliable. Basically, mine still had TWRP, this one does not. Mine would boot into the LG logo with those wonderful white words on the top left. His is completely discharged, NO TWRP or anything. Boots the LG logo breifly and basically kicks it directly into Firmware Update mode.
So basically I have to restore the D802? I used the T-Mobile 4.4.2 kitkat based rom on mine, not sure what this had, but I know it was a T-Mobile rom as the customer described. Question is, how do I install a custom recovery then? I know that mine would get detected as a T-Mobile, but since I had the luck of having TWRP, I simply wiped everything, and it would then flash via flashtool as a normal LS980.
Any ideas on how I get TWRP on it? Should I experiment using the AutoRec for the T-Mobile variant?
I was preparing an LG G2 for sale in in deleting all of my info off and restoring a backup, I managed to get distracted and wiped everything off my phone. Every. Thing. I have TWRP still installed, but when I try and boot into it, it immediately begins running OpenRecoveryScript and then boots into the LG splash screen and there it sits. I have tried going to ADB from there but I get a "device not found" message. I d/l the LG flash tool and tried re-flashing the .tot file but after it does the initial scan it just sits and unplgging and re-plugging does nothing. I d/l the LG Mobile Support tool, but I need the kdz file for AT&T and I can not locate it anywhere. Every Google search keeps pointing me back to the same page that has the tot file. A couple of questions:
1. Can I flash a T-Mo kdz file in order to get it back to a point where I can ADP into it or access the device another way, or will that REALLY hose things up?
2. Does anyone HAVE the AT&T kdz file?
3. Am I just screwed form the start?
Thanks!
with the tot file method did you change the port to 41?
meangreenie said:
with the tot file method did you change the port to 41?
Click to expand...
Click to collapse
Yes. It will recognize the phone and do all of the pre-checks. Once that is done, it just silts there. I have had that happen before, and usually unplgging the USB cable and then plugging it back in will get it going. Not this time.
CRISIS AVERTED!!! I knew I was close since I could get to TWRP (even though it didn't work correctly) and the PC was recognizing my phone. I finally loaded all of the root tools onto a different laptop and started from scratch using the LG Flash tool and VIOLA! I have my phone back.
MOD - You can close/delete if you wish. Thanks!
bradspace said:
CRISIS AVERTED!!! I knew I was close since I could get to TWRP (even though it didn't work correctly) and the PC was recognizing my phone. I finally loaded all of the root tools onto a different laptop and started from scratch using the LG Flash tool and VIOLA! I have my phone back.
MOD - You can close/delete if you wish. Thanks!
Click to expand...
Click to collapse
Congrats. I know it is a great feeling. ?
Sent from my VS980 4G using XDA Free mobile app