Related
How can we flash new ROM's onto the Universal in Windows Vista? I tried flashing PDAViet 2.00.04 to my Universal and recieved a 101 connection error. I went to the activesync website and it wouldnt install because it said that windows vista already has some tool that has outdated activesync.... well why isnt it working then?
on vista there's no more activesync but Mobile device Center
http://www.laboratoire-microsoft.org/whitepapers/17844/
Nope tried that. Wasnt working although just now I have just flashed PDAViet ROM on my Universal. Windows detects it fine and even sync's with it.
I have just tried Helmi's AKU 3.5 again and it flashed fine.
Once you've got WMDC up and runnign the sync works fine (even office 2007! Woohoo) but icant flash anything and have to use my old XP machien to do it on!
Maybe it depends on the version of the no-id flasher you use?
I tried to flash the device while in bootloader mode and wouldnt work. Does anyone know why sometimes your device remains in bootloader mode even after a soft reset? Its like there wasn't any ROM on the device? Even after a hard reset the device wont go out of the bootloader mode.
I couldnt flash My Universal, using WMDC in vista RTM. It simply doesnt work, i heard, and i think it does make sence, that the Actual Rom Update utilities are simply uncompatible with Vista. I think we will have to wait until Vista is Oficialy releast, wich is not that far away. But then, i think we will also have to wait till one of our Providers will release a new ROM, with a new Update Utility.
nuclear said:
I tried to flash the device while in bootloader mode and wouldnt work. Does anyone know why sometimes your device remains in bootloader mode even after a soft reset? Its like there wasn't any ROM on the device? Even after a hard reset the device wont go out of the bootloader mode.
Click to expand...
Click to collapse
That happened to me as well on a numerous ocasions, its really annoying. I didnt really mind though, coz i was about to flash it anyway, and then it always got back to normal.
I dont know what to say... just be careful with what you are doing.
nuclear said:
How can we flash new ROM's onto the Universal in Windows Vista? I tried flashing PDAViet 2.00.04 to my Universal and recieved a 101 connection error. I went to the activesync website and it wouldnt install because it said that windows vista already has some tool that has outdated activesync.... well why isnt it working then?
Click to expand...
Click to collapse
I´m using the Vista Business Version (Final).
My Universal would not sync so i downloaded and installed this:
http://www.microsoft.com/downloads/...6a-a72d-4aef-9663-31ce2fefbada&DisplayLang=en
Microsoft Windows Mobile Device Center Beta 3 for Windows Vista (x86)
It´s working now.
I have that installed too. It was installed during a Auto-update. Still wont update the device while in bootloader mode.
There is no driver in vista that presents the device as \\.\WCEUSBSH001 device. So the upgrade utilities cannot communicate with it.
I've tried to use the drivers from XP64, but they don't work (i'm using 64-bit vista enterprise).
not yet
I tried using Vista Ultimate x64, but no way using Windows Mobile Device Center beta 4. Xp still better for flashing devices, maybe in a few weeks we are going to test new dev tools.
heyy ppl i can't upgrade/flash my universal rom's in vista as well :-( i just upgraded my laptop to vista ultimate and well, i had downgraded my phone from AKU 3.5 to an orange branded latest rom from Orange website, now i wanna flash it to Crossbow but vista won't let me..maybe the developers here can cook something up for flashing in vista ? Anybody ?
damac said:
heyy ppl i can't upgrade/flash my universal rom's in vista as well :-( i just upgraded my laptop to vista ultimate and well, i had downgraded my phone from AKU 3.5 to an orange branded latest rom from Orange website, now i wanna flash it to Crossbow but vista won't let me..maybe the developers here can cook something up for flashing in vista ? Anybody ?
Click to expand...
Click to collapse
okay i managed to use the windows mobile center to synchronise. I will try to flash a ROM.
phamoui said:
I tried using Vista Ultimate x64, but no way using Windows Mobile Device Center beta 4. Xp still better for flashing devices, maybe in a few weeks we are going to test new dev tools.
Click to expand...
Click to collapse
is it a mistake, or are you talking about the new Windows Mobile Device Center beta 4, i only have beta 3???
yep beta 4....
nuclear said:
okay i managed to use the windows mobile center to synchronise. I will try to flash a ROM.
Click to expand...
Click to collapse
Ok i finished testing. It wont flash the ROM's in bootloader mode or in OS mode. Program installation and synchronization are functional.
phamoui said:
yep beta 4....
Click to expand...
Click to collapse
Where did u get beta4?
Vista no no to flash
nuclear said:
Ok i finished testing. It wont flash the ROM's in bootloader mode or in OS mode. Program installation and synchronization are functional.
Click to expand...
Click to collapse
OKay so basically either somebody gets the flashing tools working in vista or i'm gonna have to install XP with Vista dual boot cause i don't wanna let go of Vista. a lot of trouble to get the phone to be flashed..somebody find a solution pleeease ..Thanx ! :-(
mamaich said:
There is no driver in vista that presents the device as \\.\WCEUSBSH001 device. So the upgrade utilities cannot communicate with it.
I've tried to use the drivers from XP64, but they don't work (i'm using 64-bit vista enterprise).
Click to expand...
Click to collapse
I still try to solve this issue.
If you find any information about it, please tell me, thanks.
Of course, I will tell you if I solve it.
Hi
recently, i decided it was time to wipe my computer clean and do a fresh install (you know, its like flashing roms, sometimes fresh is better) so i reinstall win 7 ultimate x64 and for the life of me, i cannot get adb to recognize my g2 with cm7 rc1... ive searched through several threads on installing the proper drivers, installed the most recent version of htc sync, latest android sdk, and nothing... its not such a big deal, but i would like to flash to the final of cm 7, but i dont like a lot of the fluff in cm7 (adw, etc) and find it easier to remove and change things around through adb.
thanks in advance
Did you use the installer to install the android sdk? I had issues as well with that one. Removed it and just extracted the .zip package, after that it worked fine.
This REALLY is a tricky one. In the past I've had luck installing both the HTC sync software, and PDANet. Between those two all the drivers seem to work for me in Win 7 64bit.
Why not just use a file manager like 7zip to remove/add the things you want prior to flashing. Or do you just like doing things the hard way?
kamontryst said:
Hi
recently, i decided it was time to wipe my computer clean and do a fresh install (you know, its like flashing roms, sometimes fresh is better) so i reinstall win 7 ultimate x64 and for the life of me, i cannot get adb to recognize my g2 with cm7 rc1... ive searched through several threads on installing the proper drivers, installed the most recent version of htc sync, latest android sdk, and nothing... its not such a big deal, but i would like to flash to the final of cm 7, but i dont like a lot of the fluff in cm7 (adw, etc) and find it easier to remove and change things around through adb.
thanks in advance
Click to expand...
Click to collapse
See bold. Therein lies your problem.
dhkr234 said:
See bold. Therein lies your problem.
Click to expand...
Click to collapse
Unless it's specifically a problem with Ultimate, there's no reason it won't work. I run Win 7 Home Premium x64 at home and the steps I said work for me.
I run 7 ultimate 64bit and adb works fine for me.
I used the pdanet drivers.
Flash with rom manager and then install zip from card..the adwmod zip that is..take it out for you
Sent from my Vision using XDA Premium App
dhkr234 said:
See bold. Therein lies your problem.
Click to expand...
Click to collapse
I have to agree with everyone else on this. I'm running Windoze 7 X64 and adb works just fine. I also have Ubuntu 10.10 64bit and Sabayon 64bit on my HDD (yay multiboot!) and neither of them have issues either.
dhkr234 said:
See bold. Therein lies your problem.
Click to expand...
Click to collapse
i was using win 7 ultimate 64 before, and it worked just fine, im staring to think that its my actual hardware usb port on the tower, my wifes phone (mytouch slide) isnt recognized either, and i have gotten my younger sisters pc to recognize my phone no problem (except the pc is slow as dirt...
KCRic said:
Why not just use a file manager like 7zip to remove/add the things you want prior to flashing. Or do you just like doing things the hard way?
Click to expand...
Click to collapse
i use winrar to change files around before i flash it, but lately ive been having problems with the edited rom (i.e. install fails, boot looping even after a data/cache wipe, etc) i just wanted to try a different route this go around
You could try another usb cord, and make sure everything is installed under admin,and the way I got my drivers I edit the driver file and added the info for G2 (saw it in tmobile forum) and also I have no problem with win 7 x64 aswell... and I agree I don't like all the extra puff and bluff oin cm7
well, i havent been able to get a wired adb to connect, but i have gotten it to work with wirelessadb and i am now rockin a modified cm 7 final
on 3 of my computer, all 3, are stuck at 10% while installing lgmobile support tool... nothing done yet, just installing the software onto the pc.
seriously, is LG support really this bad? I had a skyrocket before and everything was such a breeze...
dustin4vn said:
on 3 of my computer, all 3, are stuck at 10% while installing lgmobile support tool... nothing done yet, just installing the software onto the pc.
seriously, is LG support really this bad? I had a skyrocket before and everything was such a breeze...
Click to expand...
Click to collapse
sorry for this double post, admin can you please delete this, not sure i know how.
Did you get this sorted out? I'm having the same issue. the install starts then stalls after the progress bar barely moves....
I didnt face that problem, I've just installed in on my PC
Check your PC
Hi, I'm back, now I know why it stuck at 10% (in my opinion)
1. Try to use it in Win 7
2. Run compability at Win 7 mode (if you use Win 8 or above)
3. Check your internet connection
Hi guys. i have a news: dont have to use LG mobile support tools anymore. Search Google for: LG Flash Tool 2014
I rooted my G3 using iRoot while having Lollipop 5.0 installed. I have just received my update from LG for Marshmallow. When I tried to do the update it told me that my phone was rooted so I can't get it. I un-rooted my phone, and tried to put everything back to the way it was, but no go. They still said my phone is rooted. The problem is that I can't do a hard factory reset. I get a message "secure booting error ...".
So after reading up on it a bit, I realized I needed to flash a stock ROM through my computer. I downloaded all that I needed, and installed LG Flashing Tool 1.8.1.1023 on my Windows 10 computer, following all the directions exactly (including replacing MegaLock.dll). The program installed, but when I wanted to run it, it told me that it couldn't find MegaLock.dll, and then asked for an ID and Password. I uninstalled it and reinstalled it many times using slightly different versions, but I had the exact same problem each time. Then I decided to try and install it on a Windows 7 machine, and it worked. So it seems that something is keeping it from working on the Windows 10 computer. Can anyone help me with this, or maybe there is another way? Maybe the dll file has to be placed somewhere else? Maybe a different MegaLock.dllis needed that is compatible with Win10? Maybe a different program? I have no idea. Any and all help would be appreciated.
Thank you.
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
what varient do u have
TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
what varient do u have
Click to expand...
Click to collapse
My computer recognizes the phone, that's not the problem. It's purely the program, I can't run it. It doesn't open.
i see try older versions of the program try googling lg flash tool do you have the megalock.dll
---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------
im sorry i just really read in full i had the issue to when i upgraded to win 10 i ended up going back to win 7 too things just wernt going well with 10 also had trouble with flash tool always failing never restoreing i was a pain i thought i messed my phone up and it ended up bein win 10 my pc has the secure boot and crap on it it even makes it a pain to dual boot ubuntu up so i just run 2 machines on my tv
A Possible Solution
alwaysdiving said:
I rooted my G3 using iRoot while having Lollipop 5.0 installed. I have just received my update from LG for Marshmallow. When I tried to do the update it told me that my phone was rooted so I can't get it. I un-rooted my phone, and tried to put everything back to the way it was, but no go. They still said my phone is rooted. The problem is that I can't do a hard factory reset. I get a message "secure booting error ...".
So after reading up on it a bit, I realized I needed to flash a stock ROM through my computer. I downloaded all that I needed, and installed LG Flashing Tool 1.8.1.1023 on my Windows 10 computer, following all the directions exactly (including replacing MegaLock.dll). The program installed, but when I wanted to run it, it told me that it couldn't find MegaLock.dll, and then asked for an ID and Password. I uninstalled it and reinstalled it many times using slightly different versions, but I had the exact same problem each time. Then I decided to try and install it on a Windows 7 machine, and it worked. So it seems that something is keeping it from working on the Windows 10 computer. Can anyone help me with this, or maybe there is another way? Maybe the dll file has to be placed somewhere else? Maybe a different MegaLock.dllis needed that is compatible with Win10? Maybe a different program? I have no idea. Any and all help would be appreciated.
Thank you.
Click to expand...
Click to collapse
I had problems with LG Flashing Tool the first time I tried to flash stock after upgrading my system OS to Windows 10. I finally got it to work by changing the compatibility mode for application file to Windows 8. I successfully flashed back to D85510L_00.KDZ after making the change I just mentioned.
Abort said:
I had problems with LG Flashing Tool the first time I tried to flash stock after upgrading my system OS to Windows 10. I finally got it to work by changing the compatibility mode for application file to Windows 8. I successfully flashed back to D85510L_00.KDZ after making the change I just mentioned.
Click to expand...
Click to collapse
Thanks, but I tried that already. Didn't work. In the end I transferred everything to my wife's Windows 7 computer and and did the flashing there. Everything ran as smooth as can be.
Hi,
I have a temprooted LG G3 (D855) with Official Marshmallow Stock ROM. I have tried to bump it using this thread, but the moment I have rebooted my device to recovery, I had no recovery at all and it has factory reset my device (don't worry, I had a backup). So I've decided to downgrade it to Lollipop or even to KitKat. I've tried to use LG Flashtool 2014. It had thrown an error on both versions (connection failed). I've read about it and found LGUP and even LGUP thrown an error. I've tried to do it agian from LG Flashtool (the old one) and it thrown this error: "CrossDL [] to [d855].SWversion()" and I've searched for this problem, and found a tutorial to remove this error (using Hex Workshop to delete the model) but Hex Workshop had stopped working when I've tried to save it. And I have a good computer (Intel Core i7 Skylake, 8GB RAM). Even before all that stuff, I had a temproot, which means every time I reboot the phone, the root just vanishing. And I've used KingRoot (which is a good root app) to root it.
Please help me. I want to install CM13 very soon.
MGSTUDIOs0mE0Ne said:
Hi,
I have a temprooted LG G3 (D855) with Official Marshmallow Stock ROM. I have tried to bump it using this thread, but the moment I have rebooted my device to recovery, I had no recovery at all and it has factory reset my device (don't worry, I had a backup). So I've decided to downgrade it to Lollipop or even to KitKat. I've tried to use LG Flashtool 2014. It had thrown an error on both versions (connection failed). I've read about it and found LGUP and even LGUP thrown an error. I've tried to do it agian from LG Flashtool (the old one) and it thrown this error: "CrossDL [] to [d855].SWversion()" and I've searched for this problem, and found a tutorial to remove this error (using Hex Workshop to delete the model) but Hex Workshop had stopped working when I've tried to save it. And I have a good computer (Intel Core i7 Skylake, 8GB RAM). Even before all that stuff, I had a temproot, which means every time I reboot the phone, the root just vanishing. And I've used KingRoot (which is a good root app) to root it.
Please help me. I want to install CM13 very soon.
Click to expand...
Click to collapse
Download a twrp bumped recovery img from the twrp site(https://dl.twrp.me/d855/), and Rashr or flashify app. Then use kingroot for your temporary root, then use Rashr or the flashify app to install recovery img, reboot into recovery, and then flash cm13 or whatever you want.
*I'm not sure about obtaining permanent root for MM on your SW version or your model(I have a vs985), but since you are flashing cm13 and not staying on stock you shouldn't have to worry about any of that mess.
You can repeat the whole process on a Windows 7 (32-bit) pc. I had the same problem while i was trying to restore my lg g3 to stock kitkat using flash tool (tot method) on my Windows 10 (64-bit) laptop. I am still unable to restore to stock on my laptop but this process works smooth on my brother's computer with Windows 7 (32-bit).
I am pretty sure changing to a Windows 7 32-bit pc will solve your problem.
startswithPendswithOOH said:
Download a twrp bumped recovery img from the twrp site(*removed because I am a new user*), and Rashr or flashify app. Then use kingroot for your temporary root, then use Rashr or the flashify app to install recovery img, reboot into recovery, and then flash cm13 or whatever you want.
*I'm not sure about obtaining permanent root for MM on your SW version or your model(I have a vs985), but since you are flashing cm13 and not staying on stock you shouldn't have to worry about any of that mess.
Click to expand...
Click to collapse
That's exactly what I did. And it just removed the recovery. I've also tried to do it through adb and it also failed. I've noticed that there is some missing information in my build.prop file, and I've tried to fill it, but it had no effect.
dksoni411 said:
You can repeat the whole process on a Windows 7 (32-bit) pc. I had the same problem while i was trying to restore my lg g3 to stock kitkat using flash tool (tot method) on my Windows 10 (64-bit) laptop. I am still unable to restore to stock on my laptop but this process works smooth on my brother's computer with Windows 7 (32-bit).
I am pretty sure changing to a Windows 7 32-bit pc will solve your problem.
Click to expand...
Click to collapse
Will it work in Virtual Machine? I have only 64-bit Windows 7 laptops... But I'll look for one. I'll try it.
dksoni411 said:
You can repeat the whole process on a Windows 7 (32-bit) pc. I had the same problem while i was trying to restore my lg g3 to stock kitkat using flash tool (tot method) on my Windows 10 (64-bit) laptop. I am still unable to restore to stock on my laptop but this process works smooth on my brother's computer with Windows 7 (32-bit).
I am pretty sure changing to a Windows 7 32-bit pc will solve your problem.
Click to expand...
Click to collapse
OK, so I've tried it and it still won't work. I was using Windows 7 Ultimate 32-bit now.
I've solved the problem with a little help from CODEFIRE team: I've flashed the tot with the G3-CODEFIRE dll which worked perfectly.
I can't post link because I'm still a new member.
Anyone knows how to close a thread or add the [SOLVED] tag? I'm quiet new here...
Sorry about my bad english.