Develop Bugs

[Q] Can you unroot without using a PC?

I'm new and I hope I'm not posting this in the wrong place or re-posting an old question, but I have been searching on this and other sites for days and haven't been able to find anything pertaining to my question, so sorry in advance If I'm not posting this correctly.
I have a rooted epic touch with rogue boot loader installed and UnNamed rom installed. I really liked the way it was running until I had some kind of malfunction happened and now the battery charge light won't shut off and the battery drains within a couple hours of standby time. the phone is only a couple months old and would like to take it to the sprint store as I'm assuming this is an obvious hardware issue. My problem is that my pc doesn't recognize my phone anymore so I can't flash back to stock and get rid of root, voiding my warranty. I have tried uninstalling and reinstalling kies and stand alone drivers multiple times with no avail. I've tried with the battery and sd card removed and have also tried on multiple pc's (2 win7 and and xp machine). every time it says the drivers weren't installed successfully and to replace the device being connected.
My question: Is there a way to revert to stock off of the internal memory of the phone? I know there are zip roms you can flash from the boot loader but I was wondering if there was a way to flash a rom from zip and install the original boot loader as well as get rid of root? Any help I can get would be extremely appreciated and again I apologize if I am wasting anyone's time by asking in the wrong place or re-asking a question.

Ok so I downloaded the Calkin's_Stock_Rooted_EK02_ROM_v1.0 and got it on my sd card via dropbox. Flashed and now have a stock rom on it which I think is a step in the right direction.
The only thing is now I have clockwork boot loader and still rooted. and still not recognizing on pc. anyone know of an unrooted zip with original boot loader?

I couldn't get my PC to recognize either of my 2 E4GT's, each due to a different reason, both issues were resolved by going through each step in sfhub's debugging checklist:
sfhub said:
This post is for the FAQ section:
Why is the install stuck waiting for device to be connected?
Your phone isn't being recognized by your PC as an Android device.
When the drivers are installed and the phone is properly recognized, you should see the following in start->run->devmgmt.msc
Code:
Android Phone
SAMSUNG Android ADB Interface
Modem
SAMSUNG Mobile USB Modem
Until you get the SAMSUNG Android ADB Interface to show up, neither ADB nor this script will work.
Here is a debugging checklist:
1) dial ##UPST# (##8778#) in the dialer and verify AP (or ALL) is checked (if CP is checked, phone won't be recognized as an Android device)
2) restart the ADB server (choose Option G to stop the server, it'll get started automatically by the script)
3) verify USB Debugging is ENABLED
4) verify USB drivers are installed (Win7-64bit see below)
5) try a different usb cable
If you are in Win7-64bit try changing the default install location for the drivers:
If you see an error like this:
Try running the CMD prompt (or e4gtauto-sfx.exe) as Administrator. Right-click on the CMD icon (or e4gtauto-sfx.exe) and select "Run As", then select Administrator.
If that doesn't work, try disabling windows firewall.
Click to expand...
Click to collapse

I went down that list and everything seemed to be in order but still no recognition by pc. I kept uninstalling and reinstalling the drivers and switching usb ports and it finally installed the drivers successfully long enough for odin to recognize it and to flash back to stock. As soon as it was done the machine stopped recognizing it again. Lucky break I guess. So I can now return it to sprint and deal with the hardware issue.
I would still like to find a zip file like the tar that I flashed that installs stock recovery and non rooted ek02 rom and kernel from cwm, if that's even possible.
Thanks Godswrath, for helping me out.

You could use wifi explorer to get files on to sd card and mobile Odin to flash the tar file back to stock....
Sent from my SPH-D710 using xda premium

Lol....I am a noob.
They make a mobile Odin? That would have saved my like 4 hours....

help did I brick my phone?

All,
I have a big problem. When I try to start my phone I get the black screen with google and the unlocked padloack, after which the screen goes dark and nothing happens anymore.
What I did before this are two things. I had been mukking around with the screen resolution (I had it set at 240 and 280, as some apps did not show up in the market) also downloaded LCD density to solve the market issue.
I then rebooted the device and entered CWM to do a backup which as far as I knew succeeded. unfortunately after rebooting, see the above.
I have tried a couple of reboots, tried restoring the nandroid (the above was the only one I had). that didn't work, so tried to connect to the PC to load a new ICS rom (original 4.0.4 by google), unfortunately my device can not go into USB mode in CMW (it comes up with UMS lunfile missing....)
so I am woring in circles. can't start the device to download a rom, can't open USM to load a ROM to start the device again.....
any help would be appriciated
thanks
Patrick

hey
flash a new ROM via fastboot then, there are enough guides
-Syn
Edit: Alternatively, flash the stock Google ROM via GNex toolkit and go from scratch.

as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?

pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
Click to expand...
Click to collapse
To flash stock images the files are on your PC, not the phone.
If you can get the phone to boot into fastboot (via vol up + vol dn + power) and get your PC to recognize it you're good to go.

thats the issue. pc cannot recognize the phone, so cannot get any files from the PC to the phone (ie. cannot get a rom file to the phone...)

pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
Either directly from Samsung or download the GNex Toolkit (You might want to use it anyways to flash the stock image), the drivers come with it.
After you installed the drivers and have you phone plugged in, go to the device manager to check if it is connected properly.

pwvandeursen said:
[snip]
thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.

pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
I had a similar issue with regard to my PC recognizing the drivers. I googled around and found that people were having success with installing the PdaNet drivers, so maybe you can try that too. I had installed the Android SDK as well as the PdaNet drivers, and I eventually got mine to work.
I would probably follow Efrant's links first though - if that doesn't work for you, then maybe you can try PdaNet drivers and/or installing the SDK.
Good luck.

Why not just do a factory reset from within recovery?
¢ £®0π π€XU$ |||

the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.

pwvandeursen said:
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
Click to expand...
Click to collapse
Good to hear you got it.

Stuck in mini pooploader (Blue Screen)

I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there

Silent Assasin said:
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Click to expand...
Click to collapse
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567

wizardknight said:
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
Click to expand...
Click to collapse
Thanks for replying. That's the guide I was using. I can't get into fastboot. ADB commands work. I tried to manually install the drivers (On the computer). Windows 7 says my drivers are up to date. I can't move forward out of mini pooploader (funny name by the way). Any ideas would be appreciated...

I meant to say that I found that thread after being stuck in mini poop mode.

9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
Click to expand...
Click to collapse
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.

plrusek said:
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
Click to expand...
Click to collapse
I followed your advice. I let mini pooploader run the blue screen with white letters. Once finished, I removed the battery, placed the battery back in and then plugged usb into computer. I then powered the phone up with the same results. I performed this task 11 times with the same results. No black screen and no win 7 driver install. The computer says unknown device. I have tried to install drivers and computers states the drivers are up to date. I have tried different USB ports. I have attempted to install HTC drivers someone posed in this forum as well as the drivers that come with SDK with negative results. I have tried to uninstall the drivers in hopes that windows would install upon recognizing device with no luck.
Any ideas? I really need to get this working. i have not had a phone for a week now

Help GNex has no OS and won't connect to a PC!

Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???

I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.

Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
stargazer127 said:
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
Click to expand...
Click to collapse

isajoo said:
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Click to expand...
Click to collapse
OK, downloaded universal naked driver 0.72, connected gnex, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, and will not allow install of of universal naked drivers, & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?

KingWickedd said:
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
Click to expand...
Click to collapse
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?

stargazer127 said:
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
Click to expand...
Click to collapse
You have to go to the device manager, double click on the "unknown usb..."
a dialog box may appear and then click on the 'driver' tab.
There u may find update/install driver button.
click on it and another window may open.
then select browse my computer for driver software and go to the respective folder where the drivers are.
then click next and it may install the drivers.
if you have installed the toolkit then you may find a folder in the toolkit's installation folder which has drivers in it.go through it if you want :good:

How to replace CWM with TWRP on the Samsung Galaxy Nexus

I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.

erich_vogt said:
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
Click to expand...
Click to collapse
I used Odin and TWRP in a .tar file. This seemed to work ok but on rebooting the phone now gets stuck on the Google logo. I assume it is a boot loop. The solution to this according to various threads is to either re-flash a stock image or to flash with a custom ROM. I'll try the latter.

I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?

erich_vogt said:
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
Click to expand...
Click to collapse
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.

erich_vogt said:
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
Click to expand...
Click to collapse
I went back to Device Manager and changed the MTP driver to the other alternative which now exists in the system. It's called "MTP USB Device" and is a Microsoft driver. This seemed to improve the situation and allowed me to see all of the contents of the folders in the phone's Internal Storage. I discovered by a process of trial and error that now I could copy files into all the folders except the folder called !ReadyToFlash. I believe this folder may have been created by TWRP when it installed. All the other folders are now behaving sensibly. I copied the Lineage 13 zip into the Downloads folder and booted the phone into Recovery Mode. TWRP 3.0.2-0 was able to install Lineage and everything seems to be working correctly although I haven't tested all the functions yet.
I notice that although the radio can see my 5GHz 802.11ac wifi it seems to be unable to connect and can only connect to the 2.4GHz wifi. I don't know if this a hardware limitation arising from the original modem or a software limitation of the Lineage modem driver. This thread, although it's just me, might give another noob attempting to reconfigure their old Galaxy Nexus a few pointers.