Related
OK my BELOVED X51v screen is on the fritz
(From an erlier post i made from a diffrent thread)
*********((Has any one else experianced flashing lines across the screen that almost looks like stactic off the the TV? I started getting it after I flashed to the newest ROM, I've tried to reflash twice, after the initial flashing, but im still getting the same problem. The "static" even showeed up on the boot screen of the firsat REflash. It seemed to get better but now I picked it back up and it was still doing it just a little bit, but enough to scare the crap out of me and let me know I didnt fix the problem even though it made it like 90% better than what it was, At first i couldn't even read the screen it was so bad. Im hoping I had a bad install with a corrupt file or somthing and not that my bassically new X51V is already broken. Im reflashing to the last rom now hopping that might fix the problem, If anyone knows what might be my problem I grately appreciate any advice. Also if this means anyhting it seems to get even worse when im playing music on it and the screen dims, it was looking fine with the back light on but then screwing up everytime that I turned the light off, I could be nothing because other times it was messed up even with the backlight on.))*******
and i cant find anyway to fix it so im thinking about sending it back to dell to see if they can either replace it or fix it, my ownly problem is i cant send it back with a "cooked" ROM. I tried to reinstall my WM5 A12 rom but when it goes to install the new ROM it disconects from my activesynct and my Windows Mobile Device Center depending on weather im trying to do it on my Vista computer or my XP. I REALLY want my x51v fixed, i tried getting the SD version of the A12 ROM but you have to make it yourself and i cont figure that part out, i can get up to the .nb0 file conversion but for the life of me i cant figure out how to make a .crc file that will work. Does anyone Please know a link to a downloaded pre-converted A12 file or atleast know how to help me figure out the stupid .crc file thanks so much in advance PLEASE help!!!
Drakey83
So Dell is going to send me a new PDA right now and I was just double checking that since I flashed back to the dell WM5 A12 ROM theres no way that they could find out that I used a Baked ROM right?! Just making sure so that my warenty Isn't discovered as void and I have to send my new PDA back.
Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.
I had what sound like the same problem yesterday.
my post is over at ppcgeeks.
"I disconnected but I did not see the phone exit bootloader mode and reset itself.
....
What should I do from here?
Reboot phone, soft reset, hard reset? - go have fun?
....
I did a couple soft resets and have been playing around with it,
I guess I upgraded right... but it was weird there at the end, instructions not the clearest to me, i guess."
mine seems to be working fine, except the weather thing.
shows
in the About section my phone reads
WM 6.1 Pro
CE OS 5.2.21041
Device Information reads
ROM version 1.05.Alltel
Radio version 3.42.30
PRL Version 30008
PRI version 2.02_011
I was kinda scared to do another hard reset b/c I had already changed a bunch of settings.
Sorry if this doesn't help you too much,
but it is nice to know I'm not the only one with this issue
.
Hmm sounds like a similar problem. But I thought it wasn't unlocked unless we saw 2.31.coke somewhere in the device information.
As far as I know, hard reset did not hurt the phone. I tried installing that unlocker 4 times then went with the original HTC rom and it still turned out just like before. It installed the rom fine
Yeah I am still concerned about how it wont go through the exitbl step...
moonwoo said:
Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.
Click to expand...
Click to collapse
Yeah, the directions can be a bit confusing over there on that thread
Basically here are the steps
Download the 2.31 unlocker
Download the ROM you want to use (my personal preference is this one for a TF2D style or this one for a WinMO 6.5 style interface that has TF2D included to switch back and for - both very stable, fast and clean and the thread is very active for help (especially if your on Verizon or Bell which can have issues)
from there, use WinRAR to extract each file into separate folders
then Put your phone in bootloader mode (press and hold power+camera+stylus in reset until 3-color screen comes up)
At this point at the bottom of the screen it will say Serial, plug it into the USB cable or cradle and it should change to USB
Start the exe in the 2.31 and follow the directions (you may get some errors about sleep4.exe just click on OK as it keeps occuring its a XP/Windows7 64 bit issue if that is what your using)
At the point where it tell you to disconect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
once complete, reboot, allow it to do its thing then reboot and go back into bootloader again during reboot you should see coke 2.31 in the upper left if so your ready to go
plug it into your USB/Cradle again and then go into the ROM folder you extracted the ROM into
Once the screen on your phone says USB again go to the folder and double click on the RomUpdateUtility.exe file and follow the directions again, it may take some time so be paitent
once the phone flashes and reboots, let it run and do its thing to the and reboot itself then (and here is an important step for stability) once it starts up do a hard reset (red+green+stylus in reset hole) hit the enter button (center of D-Pad) it will reflash the phone and then red key (send) when prompted
then go thought the setup again, this time you can actually set things up as your keeping them this time and once things are done and your at the start screen on your phone power off (not reset) the phone and then start it up again - seems doing it this way takes care of alot of little issues that will come up before they can happen
Depending on your carrier be sure to have one of the DCD Carrier Cabs as well especially for the 6.5 ROM as it is a generic ROM and some have reported needing to run the DCD Carrier Cab for the service they use to get on the internet and use GPS and the like
Hope that clears up things a bit LOL
Detroit Doug
Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!
moonwoo said:
Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!
Click to expand...
Click to collapse
Your all set to flash if in bootloader it says as your phone does SPL-2.31.CoKe
you all unlocked and ready to go ... just put your phone in bootloader mode then connect the phone to your PC "serial" will change to "USB" and then run the RomUpdateUtility.exe file and follow along with the bouncing ball, do the watusi, wipe hands on pants - whatever helps you pass the time
but follow the steps as outlined above with the hard-resets and power-offs and the like, believe me its better to solve the issues before they occur than wait and have to start over
Detroit Doug
Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!
moonwoo said:
Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!
Click to expand...
Click to collapse
Glad it worked, and Ill try to answer you concerns
1 -Now that it is unlocked go ahead and swap ROMs all you want to, the tricky part is the stock ROM, flashing back to stock can and will revert your radio (if youve upgraded it) and ca cause issues with the unlocker, but a simple run of the unlocker 2.31 again can correct it
2 - NFSFAN like other Chefs have ways of moving data/programs around when they cook up these ROMs utilizing whatever kitchen program they personally prefer that being the case how they data/programs get pushed about can create the speediness you now see in your phone by freeing up the RAM for apps and the like and pushing programs off to the side optimizing how the device should have been setup from the start
As for that, Ive been using his ROMs as well as some others for quite some time and have had little to no issues with how he places the progs and data so I wouldnt worry about it
Yeah, Live in Las Vegas now - but Michigan will ALWAYS be home Go Red Wings !!!!
Detroit Doug
Thanks Doug, for all your information. Your answers were great! Hopefully I wont need too much more help in the future. i'm learning~
Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.
hibbiejibbie3 said:
Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.
Click to expand...
Click to collapse
http://forum.ppcgeeks.com/showthread.php?t=20370
Detroit Doug
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
Check your PM over at PPCGeeks
Detroit Doug
Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
From Detroit_Doug
At the point where it tell you to disconnect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
Maybe wait longer if you can,
I reckon some pc take longer to fully recognize[process] the disconnect and reconnect procedure.
example: disconnect > wait 20-30 seconds > reconnect > wait 20-30 seconds > then continue
I had that same issue and waiting longer during this process helped
.
I can't even get to that point. With active sync on as soon as I start the unlocker RUU it gets the info from my phone and shows the current rom 3.14.605.1 ....I click update and it shows 2.31 unlocker I hit next and then the install status bar comes up on my desktop and my phone goes into bootloader mode and the active sync connection drops and I get the 262 connection error. If I start the RUU with my phone in bootloader usb mode already it does not detect my current rom and I click next. click next to 2.31 unlocker, and it goes through the same steps and I get the same error. Is there anything I have to do to my phone prior to running the RUU. My phone is a verizon xv6900 running wm 6.1 rom 3.14.605.1 with radio 3.37.78
I have the same problem with my new sprint touch. I get error 262 at 0%, did they change something in these new phone that won't allow us to unlock?
Rom is 3.03.651.4
radio 3.42.30
I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.
I ended up having to re-run the .041 unlocker and then the 2.31 unlocker and it ended up working for me. I'm not sure why I had to because I Had the same bootloader info prior to running the 2.31 unlocker in the first place. The 6.5 rom and gps rom has been working flawlessly for a week now, the only thing I had to do was call up VZW (*8889) the guy answered "account investigations" LOL I told him I had to hard reset and my phone wouldn't authenticate and he asked me to call back from another line. I told him that I had no landline and he said thats fine I can override it just call back right away whenever you get to another phone. That was on friday and I have not called back but I've been able to text, make and receive calls so I don't think I will unless I have to.
gooney said:
I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.
Click to expand...
Click to collapse
thank you! i did that and it worked for me.
yeah, it says right in the directions over there to just run the exe it will create a temp folder and run the RUU itself from there
Extracting it and running it will always cause issues
also - Ignore the sleep4.exe or whatever if you encounter it - it is a legacy exe that is called that isnt used anymore, wont affect the unlocking just hit OK through it
Detroit Doug
So here's the situation. I've had a Touch before, and unfortunately after I broke my ribs I was spaced out on painkillers (which is why I don't take them) and forgot to pull it out of my pants before they did the good ol' wash cycle.
I finally got one back, and now I can't get anything going for me. I know for a fact I can flash the device since the new one came with the original stock WM6 ROM. Not even the 6.1 ROM, just plain old WM6. After several failed attempts to get Coke 2.31 on there I finally just said to hell with it and tried the MR1 update from VZW just to make sure it wasn't my PC.
Sure enough that one worked perfectly every step of the way.
Everytime I attempt to unlock the phone though it just fails with Error 262. I've tried every way I can think of.
I tried it with the 'Enable advanced network functionality' both on and off. I've reinstalled WMDC multiple times. I've tried it while in Windows Mobile, and while on the bootloader which just gives me the stock Vogue VZW info...nothing showing it is even getting anywhere in the unlock process.
I even tried the last resort of flashing from the MicroSD which of course just said loading for about half an hour and went nowhere.
I've read threads here and on PPC backwards and forwards on how to do this.
I've done it multiple times before on the old one before I sent it to an early grave.
I'm going nuts here trying to figure out what in the world it could be that I'm doing wrong.
Help?!?
Morpheus Phreak said:
So here's the situation. I've had a Touch before, and unfortunately after I broke my ribs I was spaced out on painkillers (which is why I don't take them) and forgot to pull it out of my pants before they did the good ol' wash cycle.
I finally got one back, and now I can't get anything going for me. I know for a fact I can flash the device since the new one came with the original stock WM6 ROM. Not even the 6.1 ROM, just plain old WM6. After several failed attempts to get Coke 2.31 on there I finally just said to hell with it and tried the MR1 update from VZW just to make sure it wasn't my PC.
Sure enough that one worked perfectly every step of the way.
Everytime I attempt to unlock the phone though it just fails with Error 262. I've tried every way I can think of.
I tried it with the 'Enable advanced network functionality' both on and off. I've reinstalled WMDC multiple times. I've tried it while in Windows Mobile, and while on the bootloader which just gives me the stock Vogue VZW info...nothing showing it is even getting anywhere in the unlock process.
I even tried the last resort of flashing from the MicroSD which of course just said loading for about half an hour and went nowhere.
I've read threads here and on PPC backwards and forwards on how to do this.
I've done it multiple times before on the old one before I sent it to an early grave.
I'm going nuts here trying to figure out what in the world it could be that I'm doing wrong.
Help?!?
Click to expand...
Click to collapse
Did you read my tutorial? It is the one stickied on this sub forum. If I were you, I would try an XP computer. This usually seem to give more issues than not. Also, the 262 error is a connection error, so a simple check would be to change the USB port that you are using to connect. Finally, you could try mtty (if you feel adventurous enough).... but I would rather go to the XP option first.
Good luck and let me know how it turns out!
This is what I had to do on my Dell Pentium 4 running Windows 7 32 bit to get mine to flash. I went into Control Panel/ Hardware and sound and Changed connection settings for WM Device Center. I unchecked everything. Then I right clicked on the ROMUpdateUtility.exe for coke 2.31 and clicked on troubleshoot compatibility and for the system to run it in XP service pack 2 mode. Then I ran the ROMUpdateUtility.exe as administrator and it worked!
egzthunder1
Your guide is actually the main one I was trying to use to get this all to work out
My big problem is that I don't have any machines with XP on them around here anywhere
Even my 5-year old laptop is running Windows 7 at this point, and I don't have the old factory restore discs for it to toss XP back on there.
neuteboomt
I just gave that a try and for some reason when I uncheck all of those settings nothing sees the phone at that point, not even the updater.
I am trying to find a way to make Virtual XP Mode see the phone since over on Modaco a ton of people have managed to unlock their omnia's in XP Mode with 0 issues...I just have to get the files all downloaded to try it out.
Edit:
Well got all the files needed to try in XP Mode, and it still gives me a 262. I think I found an old image backup of my laptops XP disc though so I'm going to try to reformat my laptop and go back to XP on it to see if all this works.
I'm hoping it does, otherwise I'm going to be spending a crapload of time playing around with operating system installs
Well that image wasn't the right one for the laptop...so it was a no go...found the right image for my laptop though so it'll take a few hours to get everything all set back up on the laptop and ready to go.
I'm hoping to report back by 3PM or so today on whether or not it all worked out.
you should read through this http://forum.xda-developers.com/showthread.php?t=569922 he was having the same issue and what i suggested worked for him
Barogi44 you are the man. I have the phone unlocked now
I can't figure out why that made a difference, but it sure did and now the phone is updating with the Bell Rom on its way to having the NFSFAN ROM on it
Morpheus Phreak said:
Barogi44 you are the man. I have the phone unlocked now
I can't figure out why that made a difference, but it sure did and now the phone is updating with the Bell Rom on its way to having the NFSFAN ROM on it
Click to expand...
Click to collapse
Im glad i could help
I haven't been able to unlock my touch. I am using 2.31 unlocker, I run the RUU.exe and get up to the point where the phone shows the gray screen with the %bar. But it stays at 0% and after a few minutes a get Error 262.
I have already re-flashed to my stock ROM, but same results.
Touch (Sprint)
ROM: 3.03.651.4
Radio: 3.42.30
WinMo 6.1
Update:
I have tried on Windows 7 Pro 32-bit, and on Windows XP Pro 32-bit. Same results....
Try this...
I'm sure the thread will be locked and you'll be told to ask in the FAQ's thread or something, but I hate when that's the only thing you get... not helpful enough! So maybe I can sneak in before the lock.
I had this problem a week ago, and for whatever reason, the only thing that worked for me was: 1st, flashing to the latest stock ROM (which you already have), then turning on the phone and letting it connect to Windows Mobile Device Center (Win7) or ActiveSync (WinXP) (do the whole 'connect without configuring device thing) then run the actual unlocker BAT file (Vogue_unlocker.bat) in the 2.31 unlocker.
Trying to manually run the EXE didn't want to work - letting the BAT file do it's thing through activesync actually worked for me.
Maybe it'll help... I hope so! Good luck!
NuAngel
NuAngel said:
I'm sure the thread will be locked and you'll be told to ask in the FAQ's thread or something, but I hate when that's the only thing you get... not helpful enough! So maybe I can sneak in before the lock.
I had this problem a week ago, and for whatever reason, the only thing that worked for me was: 1st, flashing to the latest stock ROM (which you already have), then turning on the phone and letting it connect to Windows Mobile Device Center (Win7) or ActiveSync (WinXP) (do the whole 'connect without configuring device thing) then run the actual unlocker BAT file (Vogue_unlocker.bat) in the 2.31 unlocker.
Trying to manually run the EXE didn't want to work - letting the BAT file do it's thing through activesync actually worked for me.
Maybe it'll help... I hope so! Good luck!
NuAngel
Click to expand...
Click to collapse
Oh come on Nu!
Unlike most other mods, I don't simply lock the thread. I lock it and/or transfer it to the Q&A thread where I answer the question myself. Please don't say these things. I try to keep the Vogue apart from the usual MO in several other fora.
I do it for 2 reasons:
a. To keep clutter to a minimum
b. To have a nice db with solutions to many issues that people may have with their Vogues. Trust me that the Search Engine of this site works much better when you look through a single thread than when you look for threads.
@caquito07,
I am transferring your question over to the Flashing Guide Sticky thread. Please follow up over there.
@Nu,
One last thing... thanks for stepping in
Thread closed.
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