Develop Bugs

[Q] samsung drivers wont install

hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks

After installation, plug in your phone, look at your system tray for the USB icon, click it. It should show a status of installing more drivers. This can take awhile, and for a lot of people it seems to fail the last step, Android 1.0 drivers. Open control panel, system, device manager. Look for a yellow error icon. Click that, choose to install drivers manually and locally. Then select 'choose from list', find Samsung.
That should get you back on track
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#5

Were you able to unlock the bootloader? If you didn't do this, don't go installing any driver... be very careful. If you install the wrong driver in device manager, you'll screw it up. I installed the wrong driver on my main computer and I couldn't get the device manager to even recognize the phone :| I couldn't locate the right driver either because once I installed the driver, it renamed it. It was a huge pain and the only way I got this to work was by using a different PC with the correct drivers.
I have found this to be the best instructions for unlocking the bootloader. Most importantly, it includes directions on how to gain access to adb on your phone properly. Take your time and follow the instructions exactly...

Dutchy18 said:
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
Click to expand...
Click to collapse
I had the same issue, install pdanet and your phone will be recognized when in fastboot
Sent from my Galaxy Nexus using xda premium

i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks

Dutchy18 said:
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Click to expand...
Click to collapse
silly question, but after booting to fastboot, you are using the fastboot.exe, and not adb? if you type "fastboot devices" does anything show up?

no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.

Dutchy18 said:
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Click to expand...
Click to collapse
click open that yellow unrecognized device...manually choose drivers (don't do auto), and select from the list, you'll see samsung, choose the driver
that should install android 1.0...alot of people have gotten this error.
edit: another thing to keep in mind is, after installing the drivers, and fixing the device in device manager, it can still take a little bit to initialize. in your system tray there should be a usb icon, open that to see when the drivers are done

I am in the same boat. I tried for hours on 2 different Windows 7 laptops (both 64bit). I am trying to get Yakju from one of the derivitives (without unlocking the device).
Steps taken:
- Dloaded Samsung USB driver 1.4.6 & Installed: Did not recongnize in explorer or Odin (even Odin did not show a thing)
- Dladed PDA Net A302x64: Did not recognize in explorer or Odin.
Both times the GN is in Device/Printers and listed as having Android 1.0 driver. I try to manually update, but cannot seem to find driver in list (as it just has Android 1.0 driver listed). Any suggestions?

i didnt even see the "Android 1.0".. just "unknown device" all along..
i also tried on a different computer.. same issue.
about manually installing the driver.. i tried pointing him to a manual driver package i got from this forum.. it said its the same driver..
when im searching for "samsung" on the list, i dont see a relevant driver.

Well, i've saw someone else on here who was having driver issues, who also had installed both samsung & pda drivers...
uninstall both.
fresh install ONLY the naked drivers directly off samsungs website (http://www.samsung.com/us/support/downloads/verizon-wireless/SCH-I515MSAVZW -- if you're verizon, if not, you can search there). Do the install. Plug the phone in, it will start to install its usual crap. this is the long part. then, it will fail like you saw before. in device manager, you'll see the unrecognized device. Open, it will ask you to find drivers, choose "Browse", "Let Me Pick From a List", "Samsung", and then pick the driver with the date 11/25/2011
check to see if there are any other unrecognized devices in device manager, just to be sure you got em all. at this point, plugging in your phone should show the USB connected icon in the system tray. do you see this? If you click it does it say "Eject MTP"?

[Q] Bricked Verizon Gnex. Need assistance

My Verizon Galaxy Nexus is bricked. I was having issues with it receiving mobile network signal, so by using TWRP, i factory reset and in the process decided to swipe the internal space. (my first big mistake). I lost all my images, custom roms, gapps, files.
I was unable to boot the phone and decided to use the trusty ODIN back to stock. ...I've done this previously without any issues. I downloaded all the factory 4.0.4 images and attempted many times. I can't remember all the fancy lingo but I believe it continued to get stuck at "NAND write." I was also having troubles with my phone reading "fastboot error" while at the green android screen. It reads "fastboot command read error- 2147483647"
When I tried using wugfresh's gnex tool kit I was able to flash Boot, Bootloader, Radio, Recovery ... but not system. Gave me the ADB error. I'm currently unable to install the adb drivers ... or they're not being recognized because I can't boot my device and select development options.
The "1-click 4.0.4 back to stock toolkit" shows red circles for both fastboot and adb. I'm completely lost .... and frustrated at this point.
I used the "galaxy nexus toolkit" and when it executes it writes everything but also says FAILED at the end of every line. At this point I feel my two biggest issues are ADB driver so my phone's not recognized .... also something to do with the partition on the internal sd. I don't think these programs know where to write the data on my phone...........
This go around, I'm unsure what happened but I'm left with the phone, Yellow Triangle! and computer monitor icon. I was able to odin a file called "u1_02_20110310_emmc_EXT4.pit" (unsure how or where I came up with this file...) which PASSED and the phone reboots back to the green android icon screen.
I've tried many ODIN versions, three different usb cables and three computers, with all ports. I'm still getting hung up with PDA and PHONE files when trying to odin back to stock. The device shows up on ODIN and the files are reading ... it just gets hung up like the pc can't communicate with the phone.
I'm sorry for not having the language to express in detail what I'm enduring. I will be receiving a replacement device in the mail tomorrow and hoping I can connect it to the PC and hopefully have the driver's install properly.
Any and all help would be appreciated.

I am able to boot into ODIN mode and also the screen with green android with chest open. It reads in red letters "no revocery or boot img"
The device is still in locked status.
...sure hope this passes the brief Verizon inspection.

My tool failed you? I have other ideas. Pm me
Sent from my Galaxy Nexus using xda app-developers app

vabeachfc3s said:
My tool failed you? I have other ideas. Pm me
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm sorry, I tried but your profile only shows skype chat. I'm really unsure how to PM through these forums.
I was able to keep bootloader unlocked and attempted everything once more. I have no ADB access due to the phone not being able to power on and select development tools option.
Fastboot fails on everything primarily due to "partition" issues. .......... I locked the bootloader and boxed it up "as is"

LG G4 How to find correct version & model

Hello guys,
I am an unlocked LG G4 user running on Android 5.1 Lollipop.
I cant recieve updates through OTA as it always says "You have latest version of current OS". So I tried updating manually.
Since I am not very good with LG flash tools I was looking at unlocking bootloader and twrp.
The problem is :
My hardware info shows "LG H815"
Adb recognizes it as "LGF500L204da3d4 unauthorized"
A google search told me that F500L is Korean variant and now I am totally confused. Am I missing something here.
I have attached screenshots of device info.
Please guide.

The unauthorized thing comes from enabling ADB in the Developer Options. Once you do that, the very next time you connect the G4 to a computer and then run the "adb devices" command it starts the adb daemon and then tries to connect to the device, upon a connection the phone not the computer will pop up a box asking for permission to allow the connection based on an RSA fingerprint (aka the security aspect) and you have to allow that.
Without allowing that you'll never get ADB to work properly. You can try this process to get things working properly:
- Disconnect the G4 from the computer entirely
- Disconnect it from any charger too just so you're good to go
- Go into the Developer Options, revoke all using the "Revoke USB debugging permissions" and reboot the G4 right then and right there as soon as those permissions are revoked, do NOT do anything else, reboot immediately after you make that change
- Upon the reboot let the G4 boot completely and wait 2 minutes before swiping/unlocking the device back to the Home screen
- Plug in the USB cable and make sure you choose the MTP/file option, not charging
- Fire up the adb devices command on the computer and watch the phone carefully for that popup asking for permission to connect
- Choose OK to enable the connection and check the box to make it permanent for that specific computer
After that it should show you the device serial number and say "authorized." If not then you're missing something or there's some other problem, but that's how I've done this on a few hundred devices over the years and never had an issue. The other thing that could be affecting this are making sure you have the proper ADB drivers, sometimes that can be a complete pooch-screw to get working and I can't help on that front.
Pic below is what you're looking for and without granting this permission ADB will never see the device as authorized.
Good luck...

br0adband said:
The unauthorized thing comes from enabling ADB in the Developer Options. Once you do that, the very next time you connect the G4 to a computer and then run the "adb devices" command it starts the adb daemon and then tries to connect to the device, upon a connection the phone not the computer will pop up a box asking for permission to allow the connection based on an RSA fingerprint (aka the security aspect) and you have to allow that.
Without allowing that you'll never get ADB to work properly. You can try this process to get things working properly:
- Disconnect the G4 from the computer entirely
- Disconnect it from any charger too just so you're good to go
- Go into the Developer Options, revoke all using the "Revoke USB debugging permissions" and reboot the G4 right then and right there as soon as those permissions are revoked, do NOT do anything else, reboot immediately after you make that change
- Upon the reboot let the G4 boot completely and wait 2 minutes before swiping/unlocking the device back to the Home screen
- Plug in the USB cable and make sure you choose the MTP/file option, not charging
- Fire up the adb devices command on the computer and watch the phone carefully for that popup asking for permission to connect
- Choose OK to enable the connection and check the box to make it permanent for that specific computer
After that it should show you the device serial number and say "authorized." If not then you're missing something or there's some other problem, but that's how I've done this on a few hundred devices over the years and never had an issue. The other thing that could be affecting this are making sure you have the proper ADB drivers, sometimes that can be a complete pooch-screw to get working and I can't help on that front.
Pic below is what you're looking for and without granting this permission ADB will never see the device as authorized.
Good luck...
Click to expand...
Click to collapse
Ok..So I tried as per above instructions.
The only change is it's written as "device" in place of "unauthorized". The serial number is the same.
I thought it would be written as LGH815...etc etc for the H815 model. But here it's F500L...
Is this normal?

[email protected] said:
Ok..So I tried as per above instructions.
The only change is it's written as "device" in place of "unauthorized". The serial number is the same.
I thought it would be written as LGH815...etc etc for the H815 model. But here it's F500L...
Is this normal?
Click to expand...
Click to collapse
Update:
Found something interesting as well.
The phone doesn't boot into recovery using hardware keys.
I tried with adb and got into a screen showing "No command" with red exclamation.

It means you don't have a working recovery partition now so something got borked. Best case scenario: do a full factory reinstall of the stock ROM and go from there, maybe, using Odin or whatever tool you prefer, these days I have no idea what software there is to be honest.
I don't own a G4 anymore either, but if I find one in good shape for a good price, like $50 or less, I'll more than likely grab it.

br0adband said:
It means you don't have a working recovery partition now so something got borked. Best case scenario: do a full factory reinstall of the stock ROM and go from there, maybe, using Odin or whatever tool you prefer, these days I have no idea what software there is to be honest.
I don't own a G4 anymore either, but if I find one in good shape for a good price, like $50 or less, I'll more than likely grab it.
Click to expand...
Click to collapse
Maybe I should just keep it as it is coz I don't even know what rom to use and actually which model it is.

[email protected] said:
Maybe I should just keep it as it is coz I don't even know what rom to use and actually which model it is.
Click to expand...
Click to collapse
Used to believe HTC devices are tough nuts to crack but LG just blowed me away.

can get into bootloader and recovery but can't use adb or fastboot

My phone can get to the bootloader and recovery. but for somereason it won't detect any fastboot devices or adb devices. it just gives me blank. i check computer device manager, nothing shows like no "other android" exclamation mark.
i tried reinstaling adb drivers still no luck. this all happens because i went from successful groovy custom roms into marshmellow stock rom 4.21.40-223-user.zip. i tried adb sideloading the files, boot.img, etc. and something must gone wrong.
any ideas what to do? bootlooder and recovery still works, but its like the laptop can't detect the phone at all.

supaticky said:
My phone can get to the bootloader and recovery. but for somereason it won't detect any fastboot devices or adb devices. it just gives me blank. i check computer device manager, nothing shows like no "other android" exclamation mark.
i tried reinstaling adb drivers still no luck. this all happens because i went from successful groovy custom roms into marshmellow stock rom 4.21.40-223-user.zip. i tried adb sideloading the files, boot.img, etc. and something must gone wrong.
any ideas what to do? bootlooder and recovery still works, but its like the laptop can't detect the phone at all.
Click to expand...
Click to collapse
in device manager where the driver gives exclamation mark. uninstall driver. then download asus usb drivers from asus website and install. if still not works. (if nothing or unknown device shows in device manager then either sim flex is bad or there is loose connection.) open device remove and reattach sim flex on both sides if still fails. replace sim flex. order from aliexpress it will be cheap but delivery takes aproxx a month

sukhwant717 said:
in device manager where the driver gives exclamation mark. uninstall driver. then download asus usb drivers from asus website and install. if still not works. (if nothing or unknown device shows in device manager then either sim flex is bad or there is loose connection.) open device remove and reattach sim flex on both sides if still fails. replace sim flex. order from aliexpress it will be cheap but delivery takes aproxx a month
Click to expand...
Click to collapse
thanks for the input, i also tried 3 things:
1. sdcard- format sdcard to 32fat and put stock firmware. still can't read or "mount" file. its as if the SDcard not there. my laptop and other phone can read the sdcard.
2. apply update via adb sideload. laptop can't read or get any response. as if the phone isn't there.
3.hardbrick method- Intel Soc USB driver, 1.2 Connect Zenfone with computer IntelSoc Mode: i can't get pass this step. because it requires that "now back to the phone, hold power button for 10 seconds to shutdown completely, then press simultaneously the key "power" + "volume down", until phone vibrates. Or computer makes detection sound, wait a few seconds. it will add an item immediately below intelSoC in device manager ?MOOREFIELD? new devices is connected successful."
basicly my laptop can't detect anything from the phone through the usb. anybody else have any ideas?

ok. thanks. i went to a local repair shop. and the above guy was on point. the sim flex was bad and had to be replaced. everything works now. thank you.

Is my supposed non-brickable ZUK Z2 bricked????

Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie

chazhammer said:
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
Click to expand...
Click to collapse
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.

sanjay.2704 said:
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
Click to expand...
Click to collapse
Thank you very much for your suggestion, Sanjay, it is very much appreciated :good:
When I choose recovery, everything just "hangs" - black screen that doesn't go anywhere (that's why I thought that maybe there was some kind of conflict, where the phone didn't know how to chose between the two options perhaps (pure specuclation!)
I have tried the solution you suggest, but it didn't work for me.
I will re-attempt this an extra ten times or so (you never know) just in case, and let you know how things go.
This one:
(https://forum.xda-developers.com/lenovo-zuk-z2/how-to/reboot-to-edl9008-modetotally-bricked-t3720932)

OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie

For a little added information, the other recovery was: TWRP Red Wolf
(https://zukfans.eu/community/thread...r-image-error-7-installing-a-custom-rom.8347/)
While flashing this with TWRP there was an option to flash to.... I don't remember the options and can no longer consult to check, BUT at 2am, about to give up, and not knowing exactly what to select, I selected about 3 options at this stage
I believe there were something like 5 options and I selected "boot" I think, plus..?
Very stupid of course and obviously I was too confident in not creating a problem that couldn't be solved!
I have been playing around with flashing ROMs etc for the last 10 years, over 3/4 different devices and despite having read all the warnings, since over this time I have never had any issues, I kind of considered it to be almost impossible to get into a situation where things are irretrievable...so my comuppance :-/
Again, if anyone has any ideas, I would greatly appreciate

chazhammer said:
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
Click to expand...
Click to collapse
Edl cable approach would work for you.. Here is the thread guide for you..
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146..
Also I would suggest to stick to official twrp as that's more stable as compared to redwolf..
Hit thanks if it helps.

Thank you again Sanjay.
I have ordered a new lead (to cut open and attempt this intervention)!
I will let you know how I get on.

OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal

chazhammer said:
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
Click to expand...
Click to collapse
You can go ahead with qfil now.. You should see same port in qfil as well.
Once qpst is completed phone should boot up..

After some issues with the Sahara error (needed to update to edl mode and press download immediately) I finally managed to flash back to stock ROM
Thank you for all of your help!!!