Related
Pretty sure most people know how to do this but for some who are having issues with drivers n such this might help, wouldn't hurt imo.. I'm on Windows 7 Ultimate (x86)
*** Reportedly Will not work with Official OTA 1.47/2.05 Updates, only Rooted updates, I have not personally tried. The Wizards @ the dev forums are working on a fix: http://forum.xda-developers.com/showthread.php?t=714157 ***
The steps below worked for me. I had the latest clockwork recovery,Damage Control DC 3.2.2.1 deodexed and The latest rooted ota updates installed (EVO_1.47.651.1_De-odex'd_Rooted.zip, 2.05.00.06.10 update.zip)
Download and install HTC Sync Update http://www.htc.com/us/support/evo-sprint/downloads/ (if you already have it installed then click the repair option,
or better yet uninstall your current one even if it is the same one, reboot your computer and then install this one again, for good measure.)
1. I unplugged/plugged my phone into the computer a couple times,switched to htc sync mode when it asks what type of usb connection I wanted, to install more driver updates if any
and did 2 reboots on my computer to get all the drivers updated/installed and working as they should.
2. Turn off the phone, hold volume down and hold down power button to get to bootloader,
pressed Power button one more time to get to the menu where you can reboot bootloader,
rebooted bootloader once and twice BEFORE the unrooting process for good measure.
3. Download either one of the RUU Stock Roms, I would try RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe and then RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe if the first one fails.
http://shipped-roms.com/shipped/Supersonic/
Alternate Link http://tinyurl.com/2fq4dzk
4. Plug your phone into your computer, make sure ALL Drivers installed properly if any, you may already have drivers installed, but double check, switch to HTC Sync mode
and let it install any drivers, then turn off your phone and start it in bootloader (Hold Volume Down +Power button) Reboot your computer also
to make sure everything has been properly installed.
5. Then you can finally double click (right click run as admin imo) the RUU.exe and start the unrooting process, good luck!
I try it and it don't work. I mean yet it detect my ota version but after I click update than for a while it said that my phone is not plug from the computer. I'm running windows 7 ultimate 64bit, eva x58 core i7-920
Thanks for the write-up, does this take the phone completely back to out-of-the-box stock?
yang704 said:
I try it and it don't work. I mean yet it detect my ota version but after I click update than for a while it said that my phone is not plug from the computer. I'm running windows 7 ultimate 64bit, eva x58 core i7-920
Click to expand...
Click to collapse
Make sure your in HTC Sync mode or Disk Drive Mode on your phone, also try rebooting your computer & phone, plugging your phone into a different usb port, etc, have to tinker with it a bit.
jasongthang said:
Thanks for the write-up, does this take the phone completely back to out-of-the-box stock?
Click to expand...
Click to collapse
Yes.
Worked for me earlier today. Failed the first time, but i just ran it again and it went through. Thanks for the writeup!
Np glad I could help
Sirchuk said:
Worked for me earlier today. Failed the first time, but i just ran it again and it went through. Thanks for the writeup!
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
do you have to have either 1.47 or 2.05 to use this method, or will the rooted supersonic 1.32.651.1 be able to do it?
because I installed htc sync, set the phone to HTC Sync, but the phone says it cant find it on my computer.
jasongthang said:
do you have to have either 1.47 or 2.05 to use this method, or will the rooted supersonic 1.32.651.1 be able to do it?
because I installed htc sync, set the phone to HTC Sync, but the phone says it cant find it on my computer.
Click to expand...
Click to collapse
Yes it will work for that version, you only set HTC Sync mode up to install any missing drivers, then you switch back to disk drive mode if you want your computer to gain access to your phones SD card.
Tundricles said:
Yes it will work for that version, you only set HTC Sync mode up to install any missing drivers, then you switch back to disk drive mode if you want your computer to gain access to your phones SD card.
Click to expand...
Click to collapse
so are you saying the htc sync doesnt have to actually sync? the phone never finds the htc sync on the computer. But I can get the computer to see the phone and access the sd card no problem.
Thanks for the write-up it worked just like planned. And with so many people returning for some reason or another this is just what we need
Im returning one and buying another at bestbuy HEHE
so will this return the Evo to shipped stock rom IF i did the OTA update? and will i be able to root if i have the OTA update?
thanks
I had the .6 stock(not root)and OTA updated to 1.47,how can I go back to .6 stock,I ran the .6 RUU,but it said main version older and refused to downgrade,anyone knows how do I reload the .6 back?my EVO ever rooted.
As far as I've been able to find by SEARCHING the forums:
NO
Once you do the OTA update you can NOT go back or downgrade or uninstall it or whatever.
This method posted is for installing a ROOTED ota update. ie, it was hacked, and rooted prior to being installed. If you downloaded it from sprint on your phone and installed it, your are SOL for now.
Sirchuk said:
As far as I've been able to find by SEARCHING the forums:
NO
Once you do the OTA update you can NOT go back or downgrade or uninstall it or whatever.
This method posted is for installing a ROOTED ota update. ie, it was hacked, and rooted prior to being installed. If you downloaded it from sprint on your phone and installed it, your are SOL for now.
Click to expand...
Click to collapse
That sucks...oh well,thanks for the info.
They're working on a fix, but I wouldn't hold your breath. Most of the devs are taking the weekend off for one reason or another.
Here's the discussion thread:
http://forum.xda-developers.com/showthread.php?t=714157
jasongthang said:
so are you saying the htc sync doesnt have to actually sync? the phone never finds the htc sync on the computer. But I can get the computer to see the phone and access the sd card no problem.
Click to expand...
Click to collapse
Yes, sync be damned!
Thanks for the write up.
Couldnt get it to go. Tried EVERYthing mentioned. Keep running into Error 170 USB connection error. I did dl HTC sync and let all the drivers install and rebooted my PC. And the phone.
Also tried multiple USB ports.
Nada.
not sure if this is any help, but I think the person in this thread had that same error, I hate to have you dig through the thread but I want to say it was mentioned on one of the later pages. Not sure if this is applicable to what you are doing.
http://forum.xda-developers.com/showthread.php?t=723236
elegantai said:
not sure if this is any help, but I think the person in this thread had that same error, I hate to have you dig through the thread but I want to say it was mentioned on one of the later pages. Not sure if this is applicable to what you are doing.
http://forum.xda-developers.com/showthread.php?t=723236
Click to expand...
Click to collapse
Thanks but sadly I've been through all the steps mentioned in all those links.
My USB is fine as I have been using it without issue.
I definitely cannot flash the .1 or .6 RUU.
I tried liquid jesus's method and it would not go either.
I'm stumped
Have u tried to flash the ruu as a zip?
Ok I'm a HTC noob so please bear with me. I setup adb-sdk environment and windows environment variable. After that I obtained Alpharevx and ran it. Everything went fine and I entered the beta key. But then after
'Beta key accepted - thank you for participating!'
, nothing happens. It just stops. Any idea how to get this thing going?
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
JWhetstone02 said:
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
Click to expand...
Click to collapse
Thanks
Yes my phone is frogyo.
Yes it's in USB debugging mode.
Yes ran as an admin because I disabled the protection so basically all apps as admin on my windows 7.
I've read in the AlphaRevX thread where some people have had to do it multiple times before it Roots their phone. Maybe try that?
Thank you. I will try more :O I hope this won't brick my phone. I heard HTC devices can't recover from brick. With SGS you could just odin back from whatever mess you are in.
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
4GivenByChrist said:
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Hey, so I am new to this board. I myself have a Dinc2 arriving soon. My brother just got his. We are both former fascinate owners. After researching and following some how to's, my brother was rooting his phone and he got stuck while attempting to get recovery after S-off. He cannot post, but here is what stated happened:
Hey I'm having a problem with my incredible 2.
Before activating the phone (avoiding the 2.3 update) I tried rooting my phone.
1) I downloaded alpharedex and generated the code
2) downloaded the recovery mode application onto the phone
3) and placed the SU zip folder onto my phone
I was stopped at step 3 because the volume down power button procedure was not working. Instead the phone powered on normally. I attempted it many more times and it would not work.
After spending some time on it, I said screw it, I just want to use the phone. So i activated it and OK'd the 2.3 update. It shut down my phone and began to download the file but it was stopped with a exclamation point in a red triangle. I tried doing a hard reset (volume up and power button) but that did not work. So i was forced to take out the battery. When I powered up the phone again, it continued the download: the phone shut down, it began to download and froze up like last time.
Click to expand...
Click to collapse
Okay, so yes I know he shouldn't have done this. After consulting with me, I was able to get him into recovery by attempting the volume down + power procedure about a dozen more times.
Should he install the super user package and reboot? Or should he do something now to fix the OTA auto reboot problem while he still has recovery?
Edit: Because he is in recovery, could he just factory reset and flash a new rom? Apparently, when he boots the phone normally it gets to the home screen and then instantaneously reboots and attempts to install the OTA. That is where it locks up.
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
k_nivesout said:
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
Click to expand...
Click to collapse
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
deaffob said:
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Click to expand...
Click to collapse
You have it working yet? If not I would uninstall the drivers you got and then download and install HTC sync. Then uninstall just htc sync leaving your drivers. Then try again. That wokred for me when I was unlocking a friends phone.
Sent from my Incredible 2 using Tapatalk
deaffob, you seem to be pretty computer literate, if it keeps giving you issues, boot ubuntu from a flash drive and do it that way. I messed with windows for a couple hours, and it took me all of 20 minutes to install ubuntu to my flash drive, boot into it and root.
bik2101 said:
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
I fixed it by going to alpharev IRC and got a great help from attn1! He was very helpful late at night.
To those of who'd like to know, this was my situation:
-Windows 7 64bit with admin control turned off=everything has admin rights.
-Fastboot off(tried on too)
-installed HTC Sync's driver.
-tried HTC driver that's posted on AlpharevX's website.
-HTC Sync was uninstalled.
-It was froyo
-Correct HBOOT(obvious because the whole point of getting the beta key was to prevent someone using the hack with the wrong version of HBOOT)
-Tried 3 different USB ports.
-ADB SDK was installed
-JDK was installed
-environment variable path for ADB SDK was set.
-tried reinstalling the HTC Driver twice, each time uninstalling with Revo Uninstaller to clean up registry.
So even after all these, the hack still did not work. So attn1 suggested that I should try it different computer or download the flash version of Ubuntu and try it in there. I tried it on my old lap with Windows 7 64 installed. I haven't used the laptop that much so the Windows was pretty clean and new.
It worked on that laptop. The lesson is, no matter how much you take care of your windows system, I practically baby my computer and do everything to keep the optimum performance, it will get screwed up after some time. I would've never thought that it'd be my desktop Windows that was the problem.
So if you are having a problem, please try Ubuntu as that's probably the best bet.
PeterGunz said:
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
Click to expand...
Click to collapse
but there's still the problem of not being able to turn fast boot off, which i think is needed to be able to get into recovery..
get into recovery
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
+1
Yep! And I'm happy I made the switch, the SLCD screen is not bad and has more accurate color reproduction and plus who uses the SAMOLED at 100% brightness anyways..-nobody really lol.
Also HTC sense imho is waay more useable with good functionalities like the ever so good integration of Facebook compared to TW. I still can't get over that since I was conned into thinking that the Fascinate had in-app pictures but atlas it was a link to the website.. whereas HTC has that and more plus notifications!
Sorry I'm just thoroughly impressed especially since this is my first HTC Device. ^__^
Plus the rotating capacitive buttons is just super cool... :3 Now to make it work when using the camera app... >.> Anybody know if this mod exists yet?
Sent from my ADR6350 using XDA App-Dinc2 switched from a Fascinate.. :3
michaelbsheldon said:
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
Click to expand...
Click to collapse
You can download a program from the Market called quickboot It allows you to reboot into recovery without doing a battery pull. this is what I use right now in replace of the 4-in-1 reboot menu
I just got su on mine. I am an Android beginner so my experience may help. My system is a laptop running Win 7. I had installed synch and then following advice removed it with all drivers. I installed the htc USB drivers, and plugged in the phone in the proper mode. AlphaRevX will not work. So (this may be vital) reinstalled synch with drivers. Then removed synch. Got AlphaRevX to do its thing at once. So the other drivers must be there!
I tried to use the previous version of kies to upgrade my gs2 but it never worked. Update would be from:
[KF3/phone:ke7/csc:KD1] to [KI4/phone:KI1/csc:kh2]
Which I'm sure is a big step forward as I haven't been able to update forever. I thought that once I updated Kies I'd finally be able to update my phone. Now when I connect my s2 and hit update firmware, as soon as it asks to backup it loses the connection to the s2. I've reinstalled drivers twice to no avail.
Does Kies just blow as a software or am I doing something wrong.
Kies blows big time - utterly useless... useless at upgrading, useless at backing up. According to their twitter @samsungkies - "Seamless experience with Smarter Kies". That's a joke of a statement. Go with Odin my friend, much less aggro and it works all the time.
^ I so much agree to that post.
Kies never worked for me, not even when my SGS II was used with the stock rom that shipped with it. While there was an update out for quite a long time (> 1 month) it still was showing my version as being current.
Odin is so much better or just as simple: flashing from CWM.
husaam said:
Kies blows big time - utterly useless... useless at upgrading, useless at backing up. According to their twitter @samsungkies - "Seamless experience with Smarter Kies". That's a joke of a statement. Go with Odin my friend, much less aggro and it works all the time.
Click to expand...
Click to collapse
I briefly looked at Odin not too long ago, it looked sort of confusing. I'm in another country currently and spend most of my time either (50+ hours a week) working on projects here or exploring the country. As such I don't have much time to learn a new program if it's too confusing. But I'll give it a try and hopefully get to say goodbye to kies forever.
edit: Do I need to root* my s2 to use odin?
aDroidtoRemember said:
I briefly looked at Odin not too long ago, it looked sort of confusing. I'm in another country currently and spend most of my time either (50+ hours a week) working on projects here or exploring the country. As such I don't have much time to learn a new program if it's too confusing. But I'll give it a try and hopefully get to say goodbye to kies forever.
Click to expand...
Click to collapse
It's actually quite simply. Most ROMS come with only one file. That can be flashed via PDA. Do NOT, I repeat, do NOT, I repeat once again, do NOT, and again: do NOT! tick ANY option in ODIN, unless stated specifically in the ROM's instructions and even then tripple check that you're really about to flash a SGS II firmware.
So as long as you get the right firmware, do not tick anything and just flash it via PDA you should be quite safe. There's always a minimal risk, even if you do everything right but it's very very small.
Try This!
RUN Kies onces its loaded connect phone it will say connecting phone within a short period of time and error message will load, click onto the error message a new window will open, now it will have something like 4 stages. 1st stage will say disconnect cable from phone, once you have done this click on next or the follow up stage. Now this will or should Repair drivers, and now install drivers again once this has been done connect phone and phone will now load in Kies.
XP users may have to reboot PC for driver take effect.
Hope this hepls you.
PS:THIS problem only happen to me on live update, download new kies manually install no problems. Win 7 64bit
Looking at Odin for the first time can be a bit confusing. Once you know the score tho its very easy and quick. Flashing intras files for example is a complete doddle as it's 1 tar file
Sent from my GT-I9100 using xda premium
Nyssa1104 said:
RUN Kies onces its loaded connect phone it will say connecting phone within a short period of time and error message will load, click onto the error message a new window will open, now it will have something like 4 stages. 1st stage will say disconnect cable from phone, once you have done this click on next or the follow up stage. Now this will or should Repair drivers, and now install drivers again once this has been done connect phone and phone will now load in Kies.
XP users may have to reboot PC for driver take effect.
Hope this hepls you.
PS:THIS problem only happen to me on live update, download new kies manually install no problems. Win 7 64bit
Click to expand...
Click to collapse
I've reinstalled the drivers using the connection error troubleshoot, and the phone connects fine to kies. It just loses connection to kies when I try to update the firmware. When I have more time I will most likely just use Odin but I don't want to root my phone in order to do it. Is rooting necessary?
Once you get your head around Odin, its a piece of cake.
Look for Intratech's Official i9100 Firmwares thread in the Original Android Development section, you'll find everything you could possibly need in there (instructions, firmwares etc)
aDroidtoRemember said:
I've reinstalled the drivers using the connection error troubleshoot, and the phone connects fine to kies. It just loses connection to kies when I try to update the firmware. When I have more time I will most likely just use Odin but I don't want to root my phone in order to do it. Is rooting necessary?
Click to expand...
Click to collapse
OK Odin is easy just read the Q&A
link pls...
i just upgraded to 2.1 also and now can't upgrade firmware, just keeps looping in disconnecting and reconnecting never upgrading firmware
Since nobody answered yet... No u don't needa root to get Odin work
Sent from my GT-I9100 using Tapatalk
i have had the same connect - disconnect or backup problems with kies (my version is 2.0.3) and have always blamed it on kies but once i tried to restart the phone, everything worked smoothly and i could do all kinds of operations with it. My phone is rooted and the current fw version is XWKJ1 original.
Sent from my GT-I9100 using XDA App
mertakb said:
i have had the same connect - disconnect or backup problems with kies (my version is 2.0.3) and have always blamed it on kies but once i tried to restart the phone, everything worked smoothly and i could do all kinds of operations with it. My phone is rooted and the current fw version is XWKJ1 original.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
you're are correct for 2.0.3 but the new 2.1 is totally screwed up, crashed my windows even
Gavin.csy said:
i just upgraded to 2.1 also and now can't upgrade firmware, just keeps looping in disconnecting and reconnecting never upgrading firmware
Click to expand...
Click to collapse
Just read a solution that works for me on the Dutch tweakers.net website:
- In Windows fully uninstall Kies.
- Download the latest Kies version and reinstall.
After that the upgrade worked for me.
janderk said:
Just read a solution that works for me on the Dutch tweakers.net website:
- In Windows fully uninstall Kies.
- Download the latest Kies version and reinstall.
After that the upgrade worked for me.
Click to expand...
Click to collapse
do you have the link for the download, i still find 2.0.3 only, nothing directly 2.1
Windows 7pro (32bit) absolutely none of the problems listed here or on other threads (regardless of stock/custom anything) but.. Odin is easy if you follow instructions and seems much more reliable (see intratechs thread in dev section for instructions)
Sent from my GT-I9100 using xda premium
It finally worked for me, i don't know what happened why it suddenly decided to work/
One difference i noticed is i got a notification 'Samsung Modem succesfully installed' which i did not get for the past 2 hours of restarting,uninstalling ,installing. It just suddenly came when i connected the phone
Kies is really crazy as hell
I think you may just have to turn off your anti-virus/firewall software while you update. It worked for me.
OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.
Drivers
landran said:
OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.
Click to expand...
Click to collapse
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.
TheMighyLoki said:
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.
Click to expand...
Click to collapse
Yes I have. I think I did figure it out though. I put the device into "download mode" and my computer could see, and communicate, the phone.
To put my phone into "download mode" I did the following:
I connected the phone to the computer physically with USB cable
I turned phone off.
I pressed BOTH volume buttons and held the power button while phone was attached to computer.
With BOTH volume buttons still pressed, I released the power button.
The phone screen was black with a little dialog box in the middle saying "download mode"
I could then use LGFlash Tools to flash Stock AT&T TOT file back into phone. Took 519 seconds to complete the stock flash.
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.
landran said:
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.
Click to expand...
Click to collapse
It sound like you need to manually set the APN. Do a Search for your provider.. ie AT&T T-Mobile the setting is under Network/Tethering & Networks/ Mobile networks/ Access point name/ Hit Menu Button and New APN
You are the MAN / WOMAN!! Thanks for the help. That fixed it.
For posterity and to help another "noob" stuck in my case later (maybe months down the line)
This is what I've done up until now in plain text:
Used LGFlashtool to flash AT&T stock "10k" build
Went into Settings Icon>General>Developer Options>check off "USB Debugging"
Used "E980 Universal Root" from forums to gain Root access (verified with "Root Checker" from Playstore)
Used FreeGee to get TWRP recovery installed (rebooted into recovery with "QuickReboot" from Playstore).
Used TWRP recovery to install "E980 Baseband.zip" from forums
Factory Reset
Setup new phone and input APN settings (located in Settings Icon>Networks>Tethering & Networks>Mobile networks>Access point names>Menu button "New APN"/input carrier values/Menu button "Save")
Now that I know how to get back here, I'm going to scrap the stock ROM and try to do this whole process with a custom ROM. . . and another flash-a-holic is born. The learning journey continues.
Welcome:beer:
*KCCO*2SHAYNEZ*E980*
That is what this forum is for.
I have been helped out a lot from the group and I just thought it was time to pay it back. It is good to hear that you got it up and running. But one last word of advise BACK UP, BACK UP, BACK UP, and when that is done, back up the back up to the computer.
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.
Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.
Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4
BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.
Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.
Thank you for answering
yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.
Good luck man let us know what tmobile says