Related
I just got a new computer, went to flash a new rom on my fuze and... not exactly sure how to explain... but i cant... anybody know any workarounds? i've tried one and it was a failure...
What type of errors do you get? Did you try again? we're really gonna need more info than that if you want help. there are no problems with flashing and windows 7.
if you want, you could always just flash via SD
Have you tried right-clicking then "Run as administrator"?
hope this helps
http://forum.xda-developers.com/showthread.php?p=6927056#post6927056
tutorial by me
Moved as not ROM Development.
Or right click on RUU and Run as Administrator.
ThaProphet said:
I just got a new computer, went to flash a new rom on my fuze and... not exactly sure how to explain... but i cant... anybody know any workarounds? i've tried one and it was a failure...
Click to expand...
Click to collapse
You must at least explain the error you get......
I am using my win 7 laptop. Flashing frequently with no problem and NO WORK AROUNDS.....
Ok I have the LG-P999dwp version, and was in unable to do the update through the lg updater. Was told that i have latest version. I am also running win7 ultimate and the KDZ program would always crash, so i found a work around.
I downloaded the LG kdz program and the V21_00.Kdz file You can get them from here, http://forum.xda-developers.com/showthread.php?t=1179750 here are pics to help you do this on a windows 7 ultimate and should work for any version of win 7.
The pictures show you what to do.
1: open the KDZ program ( follow the instructions in the read me )
then keep the cdma and DIAG alone and choose the browse and click on the V21E_00.KDZ file.
Sorry if this has been posted but i searched and could not find anything on how to do this. I was working out a few ways to do this on win 7 without installing win xp
2:Click on read phone information at the bottom of the program.
3:Click on Upgrade Start
4:Change country to different country and change Language to english
5:click ok and this opens up the LG updater and will push the update of GB to your phone on windows 7 machine and for phone with LG-P999dwp model # (aka refurb)
thank you soo much!
Works!!! Just follow the steps exactly. My wife has a p999dwp and I have a p999dw. Ive been trying to get Gingerbread on hers for two days now (the official way). I can now find one complaint about the update, I love it. I haven't used Bluetooth yet though. Thanks so much.
Thanks... Worked perfectly....
Just in case anyone wants to know .... I put my phone back to stock and unrooted before I did the update process.... Everything went smooth, update process took about 10 minutes.. Thanks again Bullseye....
I can't get into S/W Update mode now to flash ClockworkMod ???
EDIT: Never mind...had to try it a bunch of times (volume down and plugging in) before it worked
see my only problem is everytime i try to install the lg updater tool it stops quarter of the way and doesnt move, i have a windows 7
how did u guys get the update tool to install, i run it as administrator and it starts but then stalls quarter of the way? and it told me i had to install the tool , but then i just tryed launching the update and it started the process, of course i didnt try with the phone plugged in, what do u guys think
It doesn't even want to read my phone info....it gives me Get Chiptype Error. Tried with Debug mode too-still nothing. It keeps freezing on me....I am running Win7 Ultimate 64bit.
Anyone else having the same issues. I have all the drivers installed.
you have to be in stock 2.2 froyo doesnt matter if youre rooted or not, and stock recovery, and run the tool while booted into froyo with usb debugging on .. and i dont know but i had my sd card mounted
and by the way if this worked for you THANK the freaking OP because he figured it out and you couldnt he's awesome, love you man xD
sincest said:
you have to be in stock 2.2 froyo doesnt matter if youre rooted or not, and stock recovery, and run the tool while booted into froyo with usb debugging on .. and i dont know but i had my sd card mounted
and by the way if this worked for you THANK the freaking OP because he figured it out and you couldnt he's awesome, love you man xD
Click to expand...
Click to collapse
I am running stock Froyo and I am not rooted. I have stock recovery as well. I keep getting the same error...it starts reading my phone info and then Bam! Get Chiptype Error!
yes sir , for sure so sincest your talking about the lg update tool ur telling me i have to install it with the phone actually plugged in?
doesnt really matter, i had it unplugged till the window like the screenshot came up, try reinstalling the 3.x.x drivers from LG theres a thread somewhere and then plug your device in a different usb porn and wait for it all to install
It doesn't work for me guys. Tried reading the phone info as advised-it can't complete the operation. I get the stupid error and nothing happens. Don't know how to go around that error. Tried running the R&D tool in compatabilty mode and still got the same error.
Anyone else having the same issue?
wm2485 said:
Works!!! Just follow the steps exactly. My wife has a p999dwp and I have a p999dw. Ive been trying to get Gingerbread on hers for two days now (the official way). I can now find one complaint about the update, I love it. I haven't used Bluetooth yet though. Thanks so much.
Click to expand...
Click to collapse
Do you guys click on read phone info button on the second screen as well? That's where I am getting the Chiptype Error. Have you guys tried that? I am afraid if the tool doesn't read the phone info it won't be able to update it properly and I may brick my device. Any advises?
dude i cannot get B2Cappsetup to run! sucks it just stops quarter of the way
Did you install the msi file in the kdz folder... And I only clicked read phone info at the beginning ..
Sent from my LG-P999 using XDA Premium App
try skipping the read info and just click start upgrade.
sarni84 said:
dude i cannot get B2Cappsetup to run! sucks it just stops quarter of the way
Click to expand...
Click to collapse
Does it give some kind of an error? What kind of windows are you running?
Try rebooting your PC and reinstalling it... Only thing I did was downloaded the LG updater the other day and reinstalled it ... after it installed I connected my phone and it installed some drivers...
Sent from my LG-P999 using XDA Premium App
I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)
need more info
what model number do you have, what can you get into, what cant you get into etc
lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90
i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot
DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.
Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.
zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0
same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp
still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point
still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,
I installed Osmos Os 7.1.1 thru TWRP and when I did that I then went and flashed Aroma installer( probably not the best idea) and installed pretty much all the apps, which was stupid. Now I don't have root( and can't reroot via kingroot, it fails every time).
When I tried to get back into recovery I get the sleeping Android with the exclamation mark with the "No Command".
I just want to get back into recovery so I can restore my last backup.
Any help would be greatly appreciated!
Excavator2015 said:
I installed Osmos Os 7.1.1 thru TWRP and when I did that I then went and flashed Aroma installer( probably not the best idea) and installed pretty much all the apps, which was stupid. Now I don't have root( and can't reroot via kingroot, it fails every time).
When I tried to get back into recovery I get the sleeping Android with the exclamation mark with the "No Command".
I just want to get back into recovery so I can restore my last backup.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Can you get into download mode? If you can do that, ill upload the files you need to get your phone to a rooted functional state.
Yes I can , but, when I go into download mode on the while on the computer, it doesn't read download mode and that the drivers weren't installed correctly it detects that something was connected but goes straight to the drivers weren't installed correctly.... I feel like there's no hope with this phone, I'm stuck on a 7.1.1 rom with no root, no sim card detection and no recovery. Ugh!If you think you can get me into a rooted state, then awesome!
Shadow Assassin said:
Can you get into download mode? If you can do that, ill upload the files you need to get your phone to a rooted functional state.
Click to expand...
Click to collapse
Thank you man, that would be greatly appreciated if you could send those files, just at a loss right now. I was actually looking at phones to buy if I couldn't get this fixed! But if you might have a solution then awesome, that would save me some money!
Excavator2015 said:
Yes I can , but, when I go into download mode on the while on the computer, it doesn't read download mode and that the drivers weren't installed correctly it detects that something was connected but goes straight to the drivers weren't installed correctly.... I feel like there's no hope with this phone, I'm stuck on a 7.1.1 rom with no root, no sim card detection and no recovery. Ugh!If you think you can get me into a rooted state, then awesome!
Click to expand...
Click to collapse
Your not stuck, its a soft brick, i once had that same driver problem. Give me some time to compile everything into a single zip for you to download with instructions. To fix your driver issue, ill include the lg g3 driver kit for you to install, it may still give a driver error, but youll just have to manually assign them and ill help you with that if it comes up.
Ok man, thanks, now what I didn't mention was that I can still boot up into Osmos Os, I just don't have recovery root or radio...It's like when I flashed Aroma and installed all those apps, it broke my recovery and root...I don't understand it. So is that still classified as a soft brick? Just can't do anything with trying to restore my last backup, which I still have in my TWRP folder, but with no recovery I can't restore it, along with the root issue...I mean I tried to reroot with Kingoroot and king root, but nothing. I'm hoping what you are providing me with will get me back up and running. Thank you again man. I do have ADB and fastboot working, just can't make things work in dl mode.
Excavator2015 said:
Ok man, thanks, now what I didn't mention was that I can still boot up into Osmos Os, I just don't have recovery root or radio...It's like when I flashed Aroma and installed all those apps, it broke my recovery and root...I don't understand it. So is that still classified as a soft brick? Just can't do anything with trying to restore my last backup, which I still have in my TWRP folder, but with no recovery I can't restore it, along with the root issue...I mean I tried to reroot with Kingoroot and king root, but nothing. I'm hoping what you are providing me with will get me back up and running. Thank you again man. I do have ADB and fastboot working, just can't make things work in dl mode.
Click to expand...
Click to collapse
Yea, as long you can get into download mode, then its only a soft brick. The Stump Root apps is a collection of exploits and when in doubt it can sometimes use a brute force attack to gain root. Its how i rerooted my g3 after it got corrupt.
Ok cool, so is it different than the mobile version? Because I tried the mobile version and it instantly popped up with it saying that it can't root my phone.
Excavator2015 said:
Ok cool, so is it different than the mobile version? Because I tried the mobile version and it instantly popped up with it saying that it can't root my phone.
Click to expand...
Click to collapse
Ok, then your phone is patched. So youll have to do the full restore and root. I sent the link in a PM
PM me if you need more help or if its successful or fails.
Never got the pm.
Excavator2015 said:
Never got the pm.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4FtiSFGCyvHaUlJSGREYm5RRnc/view?usp=drivesdk
When the zip is done downloading, youll extract the folders and files and run through the guide I put in there.
Ok. Thank you, now on the computer, I can't login to XDA because my wife is signed into Google plus and it's her computer. I'll take the zip and transfer it to her desktop.
Alright man, I'm copying the zip over to the computer. Are you going to be on for a while in case I need you?
When I went into download mode the computer still didn't recognize it. It told me the drivers weren't installed successfully. When I unplugged the phone from the computer they automatically installed correctly.
Now when I went in to look at the device connected, there was a yellow exclamation mark, and it said that the drivers weren't installed correctly and it gave me a "Code(10)device cannot start". I'm so lost right now, please help me out man..Lol can it be done thru ADB? I know that I don't have download mode working so fastboot is out of the question. Ugh!
Excavator2015 said:
When I went into download mode the computer still didn't recognize it. It told me the drivers weren't installed successfully. When I unplugged the phone from the computer they automatically installed correctly.
Now when I went in to look at the device connected, there was a yellow exclamation mark, and it said that the drivers weren't installed correctly and it gave me a "Code(10)device cannot start". I'm so lost right now, please help me out man..Lol can it be done thru ADB? I know that I don't have download mode working so fastboot is out of the question. Ugh!
Click to expand...
Click to collapse
Go to your device manager and uninstall all lg drivers then run the installation of the multidriver pack i included.
---------- Post added at 07:24 PM ---------- Previous post was at 07:12 PM ----------
Excavator2015 said:
When I went into download mode the computer still didn't recognize it. It told me the drivers weren't installed successfully. When I unplugged the phone from the computer they automatically installed correctly.
Now when I went in to look at the device connected, there was a yellow exclamation mark, and it said that the drivers weren't installed correctly and it gave me a "Code(10)device cannot start". I'm so lost right now, please help me out man..Lol can it be done thru ADB? I know that I don't have download mode working so fastboot is out of the question. Ugh!
Click to expand...
Click to collapse
Now if reinstalling all the drivers doesnt work, Ill set up a guide to do a full cleaning of lg drivers and fresh install. The error codes your getting are apparently just outdated or corrupt drivers, so its not a lost cause, just a bump in the road that can be fixed.
Got it fixed!!! Back to stock rooted. Now I'm flashing super su. Now I can do that thru flashify right? You left out one major detail tho...I had to check Mark board, in LG flash tool...I was stuck in the factory reset 2 screen for like 2 hours until I finally had the computer recognize download mode again. But hey, that did do the trick!! Thank you very much man!!
Excavator2015 said:
Got it fixed!!! Back to stock rooted. Now I'm flashing super su. Now I can do that thru flashify right? You left out one major detail tho...I had to check Mark board, in LG flash tool...I was stuck in the factory reset 2 screen for like 2 hours until I finally had the computer recognize download mode again. But hey, that did do the trick!! Thank you very much man!!
Click to expand...
Click to collapse
Crap, sorry for the two hour headache but glad to hear you got it running. The guide for the restore was from another forum but its instructions are on a bunch of other sites and i forgot i had the same problem you did trying to figure out why it wouldnt recognize. So idk really know where to throw credit to, I just tried to compile everything to together for ya.
---------- Post added at 01:14 AM ---------- Previous post was at 01:12 AM ----------
Shadow Assassin said:
Crap, sorry for the two hour headache but glad to hear you got it running. The guide for the restore was from another forum but its instructions are on a bunch of other sites and i forgot i had the same problem you did trying to figure out why it wouldnt recognize. So idk really know where to throw credit to, I just tried to compile everything to together for ya.
Click to expand...
Click to collapse
And i would suggest using flashfire. Flashify has been a headache on the g3 for me but no mattef what, make a backup first.
Hey, no problem man, you really helped out! And now because of that tutorial and the detail you put in, I have recovery and root again! It actually was really easy initially!
I had someone else help out before you, and we spent hours upon hours of trial and error to try and get me back to this state, now he suggested lg root tool but I told him I couldn't get DL mode working as well. So all in all, if it wasn't for people on this site helping each other out, none of us would have what we have now , or fix things on their devices.
Thanks again!:good:
My name is Ty by the way, what's yours?
Excavator2015 said:
Hey, no problem man, you really helped out! And now because of that tutorial and the detail you put in, I have recovery and root again! It actually was really easy initially!
I had someone else help out before you, and we spent hours upon hours of trial and error to try and get me back to this state, now he suggested lg root tool but I told him I couldn't get DL mode working as well. So all in all, if it wasn't for people on this site helping each other out, none of us would have what we have now , or fix things on their devices.
Thanks again!:good:
My name is Ty by the way, what's yours?
Click to expand...
Click to collapse
Just call me shadow.
You got it man!
So what 7.1 ROM do you like the best so far? Any of them you like as a DD?