Related
I need to return my phone because the earphone speaker is whacked out but I have spent the last couple hours trying to unroot it and NOTHING is working...
First I tried HTC Sync on my computer, and I get the Error [171]: USB Connecetion Error
Then I tried HTC sync on my bros computer (since I have unrooted using his laptop before with no problems) and I get a different error saying something about i have the wrong version of data utility updater or whatever.
I spent the last couple hours googleing both errors and looking for fixes, but for some reason I could not get any of them to work. I am as frustrated as can be rite now, and any help would be greatly appreciated....
I'd prefer some sort of "dumbed down" step by step process rather than being sent to a another link, because chances are I have tried that method already and I couldn't get it to work...
I also can not get adb shell to work. I installed the sdk, but it still wont show up...
any help from anybody will be greatly appreciated...
try applying the current over the air update. That took root away for many if I remember correctly.
did you enable USB debuging?
I tried searching for the ota's but they're not showing up.
also I am running dc 3.2 currently, which has debugging mode auto-enabled I believe.
So you tried using a stock rom from here to get your phone unrooted?
If you download one of those stock RUU roms it will be an exe file that will automatically install the rom to your phone...is this what you are saying isn't working?
Have you tried doing a full wipe/clear before running anything?
I had the same error when I was unrooting mine. I just unplugged the Evo while it still had the boot loader screen then ran the stock RUU. Worked like a charm.
yes. I tried installing the shipped RUU using HTC Sync, but sync keeps ****ting out on me and giving me errors. My only option seems to be unrooting my phone without using htc sync. But I have tried a couple of the methods e found, but none of them had detailed enough instructions for me to make them work....
I'v literally spent the majority of my day trying to unroot this damn phone and its driving me crazy.... I don't know wth the problem is.. I unrooted a previous EVO before, now it seems hopeless /:
Comrade P said:
I had the same error when I was unrooting mine. I just unplugged the Evo while it still had the boot loader screen then ran the stock RUU. Worked like a charm.
Click to expand...
Click to collapse
what do you mean?
I GOT IT
Hang tight fellow XDAers. Tutorial coming in about 20 min. I will post link in this thread when done. Took me forever to get past those errors too....
do the over the air update that is freshly released it will remove root and nand
Bang3r said:
Hang tight fellow XDAers. Tutorial coming in about 20 min. I will post link in this thread when done. Took me forever to get past those errors too....
Click to expand...
Click to collapse
In for this
starplaya93 said:
I need to return my phone because the earphone speaker is whacked out but I have spent the last couple hours trying to unroot it and NOTHING is working...
First I tried HTC Sync on my computer, and I get the Error [171]: USB Connecetion Error
Then I tried HTC sync on my bros computer (since I have unrooted using his laptop before with no problems) and I get a different error saying something about i have the wrong version of data utility updater or whatever.
I spent the last couple hours googleing both errors and looking for fixes, but for some reason I could not get any of them to work. I am as frustrated as can be rite now, and any help would be greatly appreciated....
I'd prefer some sort of "dumbed down" step by step process rather than being sent to a another link, because chances are I have tried that method already and I couldn't get it to work...
I also can not get adb shell to work. I installed the sdk, but it still wont show up...
any help from anybody will be greatly appreciated...
Click to expand...
Click to collapse
Link to my tutorial (you will need adb though): http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7471721#post7471721
I'd find you the link but I'm at work right now but someone has a fix for that error. Basically I got that error whenever I tried to run the stock RUU and when the phone had the bootloader screen up I just took out the USB cable, stuck it back in, and then ran the RUU again.
Sent from my EVO using the XDA App
Bang3r said:
Hang tight fellow XDAers. Tutorial coming in about 20 min. I will post link in this thread when done. Took me forever to get past those errors too....
Click to expand...
Click to collapse
You have no idea how much i'm looking forward to your guide. If it works then you my friend deserve a metal.
starplaya93 said:
You have no idea how much i'm looking forward to your guide. If it works then you my friend deserve a metal.
Click to expand...
Click to collapse
It's up: http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=743192
This works if you're rooted and NAND unlocked.
http://forum.xda-developers.com/showthread.php?t=715915
cosine83 said:
This works if you're rooted and NAND unlocked.
http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
Well...I guess I missed that one when I was tooling around, so I wrote my own. You're right. It clearly mentions needing the proper HBOOT, which I found was the key.. But it doesn't mention how to UN ROOT after you "Start Over." It's basically the same thing though...Cheers...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
Bang3r said:
Well...I guess I missed that one when I was tooling around, so I wrote my own. You're right. It clearly mentions needing the proper HBOOT, which I found was the key.. But it doesn't mention how to UN ROOT after you "Start Over." It's basically the same thing though...Cheers...
Click to expand...
Click to collapse
When I place the PC zip file on my sd card and then boot into Hboot, it fails to recognize the card.
I used simple root to root my phone and I am running the .79 Hboot.
I'm trying to follow your instructions but I am about ready to throw this god dam phone at the wall and use insurance to get another one
starplaya93 said:
When I place the PC zip file on my sd card and then boot into Hboot, it fails to recognize the card.
I used simple root to root my phone and I am running the .79 Hboot.
I'm trying to follow your instructions but I am about ready to throw this god dam phone at the wall and use insurance to get another one
Click to expand...
Click to collapse
You have the wrong H Boot. See here: http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7471721#post7471721
Should work on any .79 HBOOT in theory, but you have to change it to the .76 one before the RUU or the zip step you are having trouble with. Do Toast's step two which is found in the thread linked above.
Yesterday my roommate decided that he wanted to join the party and root his Evo after seeing the pure unfiltered awesomeness of mine, but he ran into a problem. While trying to flash a custom recovery he kept getting the an error message about a "bad block 000x0000010000" or something similar. So, unless I'm way off, I told him he must have bad handset hardware.
Well, he decided to take the phone back to the Sprint store and see if he could talk them into swapping one out due to the defect. They said no, because after running whatever tests it is that they do that there wasn't a reproducible problem. The sales person did say though, that if his phone were to "unexpectedly crash" then he would easily just replace it.
So... my question at this point, is there a way to get around this "bad block" error, or is there a way to brick the phone without it being obvious that anything voiding the warranty was done? I searched the forums about this error, but everything if found said they eventually got it to work by trying different recoveries, or they swapped out the phone. We have a tried a few different recoveries, but none are working and we have tried more times than I can count.
Its fraud. Nobody on this forum is likely to help you since its BS claims like that which caused the deductible to raide to $100.
I understand how one could see it that way, but the way my roommate sees it is that he was sold a bad device. I don't know, I'm not here to argue semantics nor ethics, I'm just wondering if anyone has some advice for the guy. We would prefer to just keep the phone if we can manage to get the device working the way we would like.
Intensentropy said:
Yesterday my roommate decided that he wanted to join the party and root his Evo after seeing the pure unfiltered awesomeness of mine, but he ran into a problem. While trying to flash a custom recovery he kept getting the an error message about a "bad block 000x0000010000" or something similar. So, unless I'm way off, I told him he must have bad handset hardware.
Well, he decided to take the phone back to the Sprint store and see if he could talk them into swapping one out due to the defect. They said no, because after running whatever tests it is that they do that there wasn't a reproducible problem. The sales person did say though, that if his phone were to "unexpectedly crash" then he would easily just replace it.
So... my question at this point, is there a way to get around this "bad block" error, or is there a way to brick the phone without it being obvious that anything voiding the warranty was done? I searched the forums about this error, but everything if found said they eventually got it to work by trying different recoveries, or they swapped out the phone. We have a tried a few different recoveries, but none are working and we have tried more times than I can count.
Click to expand...
Click to collapse
Have you tried flashing eng build and flashing recovery from bootloader?
we flashed the engineering build through the bootloader but not the recovery. The method we used to flash recovery was though adb. we'll take a look and see if we have any better luck. my roommate said that he read something about using fastboot, but I'm not sure about that. We'll give it a try.
Just be careful not to run out of power "accidentally" while flashing a new radio... that could have devastating effects on phone usage... "Hint... Hint..."
though i highly doubt that your friends problem lies with the phone itself... should try to redo all the steps... and if you can repeat the error post more details on here...
wrx4memp said:
Just be careful not to run out of power "accidentally" while flashing a new radio... that could have devastating effects on phone usage... "Hint... Hint..."
though i highly doubt that your friends problem lies with the phone itself... should try to redo all the steps... and if you can repeat the error post more details on here...
Click to expand...
Click to collapse
lol, we are running though the whole process again right now. Thanks for the suggestion, though we are trying to avoid such a devastating event.
Well... Thanks for all your suggestions! We got everything to finally work though. I don't know why I didn't think of it earlier but we tried the simple root method and let the automated process handle all the labor. We got the exact same error with this method, but the program recognized the issue and moved the recovery to a section with no bad blocks. Doing it manually didn't allow for us to chose a different section to write to. Donation can be expected from my roommate! Thanks for the great application!
I tried to search through forums and not finding anything helpfull.
I have 2.2 on my incredible. At first when I tried to root with unrevoked it would do the first reboot and then say waiting for reboot. Then it would breifly say something like waiting to settle then give me a error about lost communication and try again.
I tried a couple of times and same issue. Then after coming back to try about 2 hours later, I can't run the program any more. I get a unexpected error. Any ideas on how to fix both issues?
I followed the guide and uninstalled those programs that it listed. And installed the drivers that it needed.
do you have the latest version of unrevoked?
I do or at least I think I do. I went to their page and got it directly from them.
I got the program running again, guess my comp needed to be turned off for awhile. But I still get comm lost unexpectedly with phone error.
I can hear the usb sound being played for something being connected and disconnected. Any ideas on how to stop that?
If you ever had HTC sync installed on your pc there are two apps that need to be uninstalled. Both are called HTC 'something'. Go to Add/Remove programs and make sure both are gone.
Also, did you read the unrevoked faq? There are other programs that can cause problems if installed on your pc.
http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.11.15
can U please help me out? I'm trying to root and upgrade to Android 2.2 on my htc mytouch 3g slide but when my phone is on recovery mode, cmd adb doesnt show my phone is in recovery, all its shows is that my device is in offline mode....I can't move to the next step without this.....Please help me, I need specific instructions.
Thanks
Flo_baby:
I would go to the MT3G forums, and start there. U likely wont get alot of help in the Droid incredible forums. Since its two different phones and one is cdma the other is gsm they are also two different beast entirely
Sent from my DROIDX using XDA App
Okay, last week, my old droid died in it's sleep. I'm currently unemployed and a friend was kind enough to give me his old Incredible. He has it rooted with CyanogenMod, and I have been trying to activate it on PagePlus. I have not been able to OTA activate it as is, and I've read it's because of the non-stock mod flashed on. I've been scouring these and similar forums for the past week, going through solution after solution to no avail. It's become a time-sensitive issue.
What I have done so far:
Downloaded the s-on and pb31img.zip: The s-on thing flashed properly, but when I try to flash the PB31IMG.zip, it just says installation aborted. I've tried downloading the zip file from multiple sources, in case it was an issue with the file. I've tried flashing Jellybean just to see if there was an issue with flashing any other roms at all and it worked fine.
Downloaded, installed, and updated HTC Sync and the correct RUU to go with my baseband. I can not for the life of me get either of these programs to recognize my phone while it's plugged in, despite the phone and computer separately recognizing each other and being able to interact normally otherwise. I believe this to be a driver issue, and I can not find the appropriate driver. All inquires to the correct one have guided me towards getting the SDK package, downloading the driver from there and installing it. I did this. When I attempt to search for drivers in the designated folder, it tells me that it can't be installed correctly. I have tried this from two computers with Windows 7 to the same effect.
I would appreciate any help on this asap, as I am waiting on several employment-related calls and have reached my wit's end on finding a solution on my own.
Did you tried to flash stock rom?
May be this helps
doug piston post, just found it in a quick search on the web
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
Hope it helps mate.
Sent from my GT-S5830i using xda app-developers app
axyllum said:
Did you tried to flash stock rom?
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
Yes, I did. It did not work. That, from my understanding, is what I was attempting to do with the PB31IMG.zip.
axyllum said:
Did you tried to flash stock rom?
May be this helps
doug piston post, just found it in a quick search on the web
Hope it helps mate.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
I appreciate the quick search, but I have done those things to the letter multiple times and described doing them as such, as well as the issues I encountered.
IanStraka said:
Okay, last week, my old droid died in it's sleep. I'm currently unemployed and a friend was kind enough to give me his old Incredible. He has it rooted with CyanogenMod, and I have been trying to activate it on PagePlus. I have not been able to OTA activate it as is, and I've read it's because of the non-stock mod flashed on. I've been scouring these and similar forums for the past week, going through solution after solution to no avail. It's become a time-sensitive issue.
What I have done so far:
Downloaded the s-on and pb31img.zip: The s-on thing flashed properly, but when I try to flash the PB31IMG.zip, it just says installation aborted. I've tried downloading the zip file from multiple sources, in case it was an issue with the file. I've tried flashing Jellybean just to see if there was an issue with flashing any other roms at all and it worked fine.
Downloaded, installed, and updated HTC Sync and the correct RUU to go with my baseband. I can not for the life of me get either of these programs to recognize my phone while it's plugged in, despite the phone and computer separately recognizing each other and being able to interact normally otherwise. I believe this to be a driver issue, and I can not find the appropriate driver. All inquires to the correct one have guided me towards getting the SDK package, downloading the driver from there and installing it. I did this. When I attempt to search for drivers in the designated folder, it tells me that it can't be installed correctly. I have tried this from two computers with Windows 7 to the same effect.
I would appreciate any help on this asap, as I am waiting on several employment-related calls and have reached my wit's end on finding a solution on my own.
Click to expand...
Click to collapse
Reflash soff and then just flash touch of blue and you can activate on page+ from there and if you want cm back just flash cm7 and the gapps because a factory wipe in recovery won't make you reactivate
Sent from my ADR6300 using Xparent ICS Tapatalk 2
Thread moved. Please post in the correct sections of the forum, all questions belong here in Q&A, unfortunately ticking the "Is this a question" box doesn't automatically put it in here.
Thanks
AvRS
I would get s-off back, as it will not affect activating. Then either do this ruu http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip, thru hboot, or as stated earlier reroot and flash the stock 4.08.605.15 rom or Touch of blue. If the ruu dosent work, try reformating your sdcard fat32 and then try again.
IanStraka said:
Okay, last week, my old droid died in it's sleep. I'm currently unemployed and a friend was kind enough to give me his old Incredible. He has it rooted with CyanogenMod, and I have been trying to activate it on PagePlus. I have not been able to OTA activate it as is, and I've read it's because of the non-stock mod flashed on. I've been scouring these and similar forums for the past week, going through solution after solution to no avail. It's become a time-sensitive issue.
Click to expand...
Click to collapse
Page Plus doesn't care a hoot if you've got a stock ROM, CyanogenMod, are rooted, or any of that stuff. And they certainly can't tell if you are s-off or s-on. I have had zero issued doing OTA programming on my Dinc regardless of the many ROMs I've had on it. I've always just dialed *22890 to activate and *22891 to update the PRL. Granted, I haven't changed my phone number or deactivated in quite a while...
But yeah, like others said, get s-off back if you at all can. If you flash Touch of Blue or another stock-based ROM, you will have more access to manually programming it that you can get with CyanogenMod.
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