Related
Hello everyone,
I have a N1...just got OTA updated to FROYO 2.2...
Just opened the boot loader for the first time...
then I just rooted it...
Now I am trying to get the AMON RA RECOVERY on their so I can use a cool rom like modaco ect...
I have been reading and having a hard time with this on the mac...I was using the terminal ect...and I keep trying to do the steps but it won't work...I must be doing it wrong...
Can anyone please give a picture tutorial or good step by step on what to do once you open the terminal...
I have put the RA recovery on the sd card and tried getting it to write to the sd card...
I also put the recovery in the fastboot folder trying to do it that way but no luck...
If anyone can help this newb I will donate paypal...
THANKS!
All commands using your mac should be preceded by ./
ie: ./adb
and fastboot is: ./fastboot-mac
./fastboot-mac flash recovery recovery.zip
Did you download the mac version of the sdk?
Make sure the files adb-mac and fastboot-mac are in the same folder as your recovery zip file. These files are in the tools sub folder in the sdk folder (or just put the recovery.zip in the tools folder).
You need to change directory (cd) so you are running all commands from the folder with adb-mac, fastboot-mac and your recovery.zip (could just be your tools folder in the sdk).
When you hook your phone up via usb, power on while holding the trackball to get into fastboot. Then apply the commands as shown above or in the tutorials (http://forum.xda-developers.com/showthread.php?t=611829).
Thanks so much buddy...I didn't think you needed the SDK stuff for the mac because I didn't see it in my tutorial =) thats probably why its not working duh! Well I was able to unlock bootloader/root without the sdk but I guess I need it now...I will download all of it and keep you posted on what happens my friend thank you!
Is it also possible to add the recovery via a windows pc as well? I might try that because I already have sdk on my windows 7...if so do you have a tutorial for doing it on windows?
THANKS!
rayman121985 said:
Thanks so much buddy...I didn't think you needed the SDK stuff for the mac because I didn't see it in my tutorial =) thats probably why its not working duh! Well I was able to unlock bootloader/root without the sdk but I guess I need it now...I will download all of it and keep you posted on what happens my friend thank you!
Is it also possible to add the recovery via a windows pc as well? I might try that because I already have sdk on my windows 7...if so do you have a tutorial for doing it on windows?
THANKS!
Click to expand...
Click to collapse
Windows is the same as I said above. Check out the link I posted for a tutorial:
via fastboot
Code:
Copy recovery-RA-nexus-v1.7.0.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-nexus-v1.7.0.1.img
I can boot up to use my phone and whatever. Only problem is that, i try booting in recovery, and it just stays on initial nexus x logo. I use 4ext touch recovery. I then flashed CWM. And still stay on initial nexus x logo. Please help.!! D; -
Leo,
time to learn fastboot--
although with cwm not flashing maybe you lost root--did you ever get partitioned for ics and have 4ext working or any recovery working?
either way you could try these ideas below--
did you buy paid version and do you have sdk on pc and where is fastboot.exe? Tools folder?
---------- Post added at 04:25 AM ---------- Previous post was at 04:00 AM ----------
if you paid, there is a dl link on 4ext OP page you can click on and it will dl you a .img you can fastboot to get recovery back.
one should also be saved on your sdcard
not sure whether it matters if paid or not
put in your tools or fastboot.exe folder, cd to that folder
have phone in fastboot mode
fastboot devices to check phone recognized
fastboot flash recovery recovery.img if recovery.img is exact name of img file
then fastboot reboot-bootloader
one time time I had to type fastboot erase system before i fastbooted the recovery to get it to work
good time to back up anything you can as in sdcard and phone stuff if you have a non root required bu program like MyBackUp Pro
i have lost recovery a couple times before with ics roms
i got to call it a night and will be on road all day tomorrow
if you don't get it someone else will offer help
ken
did the recovery stopped working right after installing blackrose?
is ur bootloader locked?
as ken suggested u need to fastboot recovery.img
Sent from my Nexus One using Tapatalk
rugmankc said:
Leo,
time to learn fastboot--
although with cwm not flashing maybe you lost root--did you ever get partitioned for ics and have 4ext working or any recovery working?
either way you could try these ideas below--
did you buy paid version and do you have sdk on pc and where is fastboot.exe? Tools folder?
---------- Post added at 04:25 AM ---------- Previous post was at 04:00 AM ----------
if you paid, there is a dl link on 4ext OP page you can click on and it will dl you a .img you can fastboot to get recovery back.
one should also be saved on your sdcard
not sure whether it matters if paid or not
put in your tools or fastboot.exe folder, cd to that folder
have phone in fastboot mode
fastboot devices to check phone recognized
fastboot flash recovery recovery.img if recovery.img is exact name of img file
then fastboot reboot-bootloader
one time time I had to type fastboot erase system before i fastbooted the recovery to get it to work
good time to back up anything you can as in sdcard and phone stuff if you have a non root required bu program like MyBackUp Pro
i have lost recovery a couple times before with ics roms
i got to call it a night and will be on road all day tomorrow
if you don't get it someone else will offer help
ken
Click to expand...
Click to collapse
Thanks Ken, I will go through your steps later on. And I wasn't able to be partitioned, my command gave me error: cannot find hboot_brcrust_210-8-218-ICS.nbo
HTCLeoSence3.X said:
hboot_brcrust_210-8-218-ICS.nbo
Click to expand...
Click to collapse
Just to make sure you did the right thing. Extension isn't nbo, it's nb0.
Sent from my Nexus One
HTCLeoSence3.X said:
Thanks Ken, I will go through your steps later on. And I wasn't able to be partitioned, my command gave me error: cannot find hboot_brcrust_210-8-218-ICS.nbo
Click to expand...
Click to collapse
It could be that you didn't specify correct path to the nb0 file.
so i have to put c:\USERNAME\program files\Android\android-sdk\platform-tools\hboot_brcrust_210-8-218-ICS.nb0
the nb0 is a zero not o nb(zero)0
put your android sdk on root of c drive not in programs
then open command window and after your user name type cd/
at the C:\> prompt type cd Android/android-sdk/platform-tools then hit enter and you should see-- (btw, not sure if command line is case sensitive as you have upper and lower case "android"
C:\ Android\android-sdk\platform-tools right after this line type fastboot devices do not hit enter first
you should see your phone ID# HT******* then you can type fastboot commands when you have phone in bootloader (fastboot) mode
assume your fastboot/adb stuff is in platform-tools. i have an older version of sdk and only use tools not platform tools. but you should have adb.exe and fastboot.exe and two adbWin dll's. an Api and UsbApi
btw if you have set up sdk correctly as you said you have exp with it--you need to have set your environmental path also
if you haven't review sdk setup in wiki, as you need to see your phone after you type fastboot devices before you can go further
also are your drivers installed and did you review the posts by efrant on adb and fastboot explanation--good info if you don't already know it
---------- Post added at 03:15 AM ---------- Previous post was at 03:02 AM ----------
a note
i guess with br installed you may not need sdk to run fastboot for br stuff. i don't do it that way so someone else may be able to offer advice. still need correct path to fastboot.exe folder drivers installed per br OP. but since you showed us the path to tools assume you are all setup with sdk and i prefer it that way myself.
Thanks man. Helped a LOT. Now running ICS. I swear thanks a million.
Sent from my Nexus One using xda premium
Welcome and enjoy------
Hi all. Quick notice:
Usual disclaimers apply.
This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.
Okay cool... but what is an insecure boot.img?
An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin
adb shell
su
mount -o remount,rw /system
exit
See more here: External Link
_____________________________________________________________________________________________________________
To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).
A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/
To boot this boot.img:
must be in the platform-tools folder in the android-sdk
must be in fastboot mode (power+vol-)
First use: fastboot boot "boot.img" (no ")
Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**
**Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.
Thank you for helping!
-fkrone
-Ranguvar
-USSENTERNCC1701E
This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)
DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.
Click to expand...
Click to collapse
Please Lock!
Placeholder reserve
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
I wouldn't be lazy and do it myself but PC is off
Sent from a phone
Click to expand...
Click to collapse
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Ranguvar said:
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Click to expand...
Click to collapse
Pull it apart in hex editor
Sent from my HTC Explorer A310e using xda app-developers app
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
Sent from a phone
Click to expand...
Click to collapse
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
USSENTERNCC1701E said:
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
Click to expand...
Click to collapse
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
I could probably do it without this, but it probably wouldn't mount data/media (what emulates the SD) so it would be relatively useless as that's where zips are
Also this might prove useful: http://forum.xda-developers.com/showthread.php?t=1494036 (requires Cygwin or Linux environment)
Harry GT-S5830 said:
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
Click to expand...
Click to collapse
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
USSENTERNCC1701E said:
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
Click to expand...
Click to collapse
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Harry GT-S5830 said:
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Click to expand...
Click to collapse
Lol, I'm having a hell of a time getting Slax as a cooperative VM, might have to go all out with ubuntu
Got it!
Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored Would be nice if you can mention me in the people helped to create this recovery
http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror
Dammit, beat me to it!
Serves me right for making dinner first
http://ompldr.org/vZ2ExYQ/recovery.fstab
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
pikachukaki said:
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
Click to expand...
Click to collapse
That's not quite how it works. These .img files we are talking about are pictures of the stock version of those paritions. Try reading this article for an explanation of Android partitioning.
There is also a great graphic here. The site is in Spanish, I haven't used Google to translate it, but the picture there is in English. Take your time with it, there's a lot of info there.
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Stryder5 said:
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Click to expand...
Click to collapse
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
USSENTERNCC1701E said:
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
Click to expand...
Click to collapse
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Stryder5 said:
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Click to expand...
Click to collapse
Woops, wrong thread.
Yes, if you push the su binary from a superuser flashable zip to /system/bin/ and chmod 0655, plus the superuser apk, you will have permanent root after.
Also, there is a recovery.img now, so you can test that out, if it works, flash it from fastboot, then flash a superuser zip from that recovery.
Thank you for getting it (recovery.fstab), looks like someone beat me to it though!
Sorry for late response I have to sleep as I'm in last school year
Ill cook up a recovery just to make your efforts worthwhile
It's in OP, its probably 99.9% the same as the other guys so i'm not going to make duplicate thread, use who evers recovery you wish.
____________________________________________________________________________________________________________________________________
Reason I say fastboot boot first is because it allows you to boot the image without permanently (well, unless you flash another over) flashing a partition without knowing it works.
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Stryder5 said:
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Click to expand...
Click to collapse
Not at my comp now or I'd upload it, bit of you rip open the fa Tory image from the Google servers you should find it
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
On a side note, what possessed you to do that?
Well, long story short my friend royally screwed up his phone.
He screwed up the kernel and even the Recovery. Don't ask how.
We even connected the phone and ADB didn't work on bootloader. But after we went into fastboot and tried a restart it worked. So.. we used fastboot to restore the phone.
Notes before you start: Use command prompt and cd to the directory for your sdk tools. In my case, I simply used the 'data' folder for the Toolkit that was released here that had the sdk tools like adb.exe and fastboot.exe . MAKE SURE you copy the associated recovery zips and ROM zips to the very same folder to prevent complications and for the commands to work like a charm. Finally, uninstall the drivers for your phone and reinstall them (if you need to only, as we had connection issues.. yep he royally screwed up).
Boot into bootloader then select fastboot and hit the power button. Keep it on the fastboot screen. Now you can proceed.
Here is what I did:
fastboot erase cache
fastboot flash recovery recovery.zip *rename your recovery zip to 'recovery.zip' and make sure it's in the same folder as the sdk tools*
You can now then boot into recovery and write the ROM or even use fastboot to write it with the following:
fastboot flash zip rom.zip *once again, rename your ROM zip to rom.zip*
I only put this out there to help those who screwed up their recovery and can't even get the Toolkit to execute commands using ADB.
Good luck!
Yeah, fastboot on pc then in command you clear cache and install recovery. I got into a boot cycle and this fixed it.
lopuandroid said:
Yeah, fastboot on pc then in command you clear cache and install recovery. I got into a boot cycle and this fixed it.
Click to expand...
Click to collapse
Glad it worked. Yeah, for some reason my friend's computer was being really fussy. It wouldn't detect the phone or anything, and ADB was rendered useless. We reinstalled the drivers so many times.. And used 2 different laptops.. Thank God fastboot worked. Hopefully this helps anyone else in the same **** zone. I know the heart sinking feel when your Recovery won't work and you only get the bootloader to work..
Here is the story in a nutshell I flashed xdabbeb's bootstack, then his rom. Then I did something stupid such as wipe everything folks, I mean everything. So my phone then restarted and I am able to get into recovery twrp 2.7.
I have tried in twrp to sideload, mount neither which work.
I have my drivers installed it says in device manager when I plug the phone up for download mode
android- galaxy nexus adb
and under ports it says LGE AndroidNet for VZW ADB Interface com41
I tried lg flash tool, tried with old vs98010b rom
pid:
imei:
model:
dll: vs980
bin: vs98010b_13.tot
swv:
swov:
model information check fail!
00000000
I really need help guys, are there any adb commands I can type or are there any drivers I need to install
Ok when i hold the up and plug in it takes me to fastboot
[500] fastboot mode started
[550] udc_start()
[720] reset
[730] portcharge
[740] reset
[750] portcharge
and the device only registers as android under other on my computer
i've installed lg drivers
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
timenewton said:
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
Click to expand...
Click to collapse
Download mode is not going to work because the laf partition (this allows for download mode to work) is wiped when you flash xdabbeb's bootstack in favor of fastboot mode.
I suggest you pm xdabbeb; he will guide you on the steps to using the necessary fastboot commands to get your phone working again. He's already helped a few people that were in the same situation as you are in right now.
Fastboot is good because you can write certain partitons at a time without having to .tot and wipe your whole phone.
You could also flash his xdabbeb_vs98024a_laf.zip http://www.androidfilehost.com/?fid=23329332407586639 file in TWRP 2.7 to restore download mode, but you will end up wiping your whole phone by using the LG Flash Tool, even your sd card when you restore your phone.
You said you "wiped everything", I'm not sure if that means your sd card too, if so, then that might be the easiest thing to do since you still have access to recovery. You will need an otg cable and a flash drive to mount the flash drive in TWRP 2.7 and flash the file, unless you can side load the file with adb.
Either way, like I mentioned earlier, it might be a good idea to pm xdabbeb first.
Hey my phone is already wiped even sdcard, but the thing is i cant flash that file because I can not get it on my phone. So ill ask xdabbeb the fastboot commands. Yeah and I read about the otg cable, ordered one of those babies should be here this saturday and hopefully it will mount my flash drive in that case id be golden untill then ill see what mr xdabbeb has to say.
cant sideload
everytime i try to sideload the file it just says cant read file or something like that
And I really appreciate you responding. Always nice to get support from somebody when your just sitting here and your phone seems like it hasnt been working for an eternity. Almost depressing not hearing from anyhbody and just seeing all the views but no replys. Thank you
Hey there...Fastboot is about as basic/simple/reliable as it comes. If you have adb/fastboot set up properly then command is:
fastboot flash <partition> <filename>
for example:
fastboot flash recovery recovery.img
In your case, you claim to have a working recovery (twrp 2.7), but are unable to copy files from your computer to your phone. It sounds like you don't have the proper drivers installed so that you can use adb from recovery. This is a common/known issue with windows and I believe I replied to you in the rom thread already about this, but you need to install/use Koush's universal adb driver and simply copy the rom file over to your phone using the following command:
adb push <filename> /sdcard/
After you have the file there you can flash it as normal in recovery.
If you want to use a kdz/tot method to restore your phone, just download the laf zip file from my thread, extract the laf.img file from the zip, and use the following command to put it in place:
fastboot flash laf laf.img
Then you can go about the tot restore method described in the thread here. You don't need to put the tot file itself on your phone. It just needs to be on your computer.
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
timenewton said:
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
Click to expand...
Click to collapse
Wait, I'm confused here a little bit. Are you trying to do sideload mode in TWRP or are you using fastboot mode?
And the command you typed is not correct fastboot flash recovery laf.img...you don't want to do that...this would flash the laf.img in your recovery partition.
xdabbeb referenced two methods to you...one was pushing a Rom to your sdcard and then flashing that Rom in TWRP to get your phone booting...the other was to flash the laf.img file and do a .tot if that's what you prefer.
It seems like you want to do a .tot restore, so do the second method xdabbeb suggested.
Get into fastboot mode and type fastboot flash laf laf.img
Make sure you use the correct laf.img...you can extract it from the zip in my previous post/link.
After this your download mode should be working again.
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Even when i try to flash the laf it keeps saying waiting for device. I have the drivers koushu installed and lg
timenewton said:
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Click to expand...
Click to collapse
Yes, download xdabbeb's laf.img, it's the link I gave you originally. You will have to take out the laf.img file from the zip file that is called xdabbeb_vs98024a_laf.zip
The recovery command he gave was just an example, there was no need for you to use it.
Yes, flashing the laf.img will fix your download mode and you will be able to do the .tot method.
What am I suppose to do about it saying wiating for device, its not detecting it
timenewton said:
What am I suppose to do about it saying wiating for device, its not detecting it
Click to expand...
Click to collapse
That sounds like a driver issue. Reboot your computer and turn off the phone and start again. See if that helps. You can also remove the drivers and re-install...I suggest you reboot your computer every time you install new drivers.
EDIT:
Are you using a newer adb.exe from your android sdk? If you have ioroot25 installed on your computer I suggest you use the folder/files from there. It has a newer adb.exe in there; put your laf.img file in that folder too if you do use that instead, and run the command prompt from within that folder.
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
timenewton said:
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Click to expand...
Click to collapse
timenewton said:
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
Click to expand...
Click to collapse
For me it shows up under "ADB Interface", but I don't have the universal driver installed.
I didn't realize it wasn't installing the driver for you.
You have to get that driver going or you won't be able to get your phone fixed. Maybe try a different usb port or a different computer.
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
timenewton said:
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
Click to expand...
Click to collapse
Yeah, it should work. I've read posts by others stating that it works.
Yep just reinstalled the universal drivers, plug phone up into fastboot and still get the same result
Can you perhaps send me that driver you have? Because I know if you have that one and it works for you it SHOULD work for me. Murphs law is killing me. I can pm you my email address