Hi there!
I was wondering if there is a way to recover my phone after I have accidentally deleted all the system partitions using r/w access command in an attempt to recover the phone's internal memory which was showing 8gb rather than 16gb. I know this may have been a stupid thing to do but from what I have searched so far nothing seemed to solve the memory issue. I thought I could manually write the partitions but the phone won't even start and when I try fastboot devices it doesn't show the serial number and with other fastboot commands it stays on "waiting for device" for ever. Phone model is Nexus 4 E960 16GB(Mako).
Please help! :crying:
Dos anything appear in Windows device manager when you connect it to the computer (assuming you use Windows)?
After I have installed all the drivers it appeared Android device in Windows Device Manager and when I clicked appeared Full JellyBean on Mako with an exclamation mark. Thing is, at least as I have red so far, my Windows 10 can't fully recognise my phone via USB. This makes the Android device section disappeare from Device Manager and I just pray for it to appear. I will be using a Windows 7 tomorrow, I am curious what is going to happen.
Related
Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
wakers said:
Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
Click to expand...
Click to collapse
Have you got Android SDK installed on your PC, Im sure the driver is in there...android .1.0 driver I think..
Without Android SDK you cant use fastboot flash for clockwork image..
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Did you install and launched HTC sync? It should install all the necessary drivers.
f.
Sent from The Galactic Empire using the Dark Side of The Force
wakers said:
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Click to expand...
Click to collapse
Ok try this.... shut phone down, boot (volume down and power button) selected fastboot so it turns red, put the files into android-sdk-windows\tools. i-e the clockwork image and fastboot files
Plug usb cable in.
In "windows search program files" type cmd
now type cd c:\android-sdk-windows (unless you placed the android sdk somewhere else!!)
type cd tools
Type fastboot-windows flash recovery recovery-clockwork-2.5.1.2-ace-modaco-r2.img
When done type fastboot-windows reboot
You should now have CWM.
Now I know you may have tried this but It would help to find out what happens if you haven't already do so.
EDIT ...I also ask this because my laptop doesn't do anything either when I plug in usb cable in fastboot mode..im on windows 7....
Just trying to help...
Really appreciate the reply.
I got a "cannot load" Error.
I think its down to a driver for my phone when in the fastboot mode.
Whats might shed some light on something for someone with a bit more windows/android knowledge than myself is
When the phone is in Fastboot USB mode in Device manager the phone is listed as Android Bootloader interface but when i type into cmd "adb devices" nothing is listed.
When the phone is switched on normally and syncing with HTC sync in device manager the phone is listed as "my htc" and when i type adb devices in cmd, the message adb server is out of date killing...
then daemon is started and the device shows in my list ?
But HTC sync stops working ?
And the internet on my laptop stops working bizarrly.
I'm really scratching my head now lol
I'm thinking it must be something to do with not having the correct driver for Fastboot USB mode ?
Finally sorted it, had to remove the phone from device manager and delete the driver.
Then went into programs and features and removed everything to do with HTC.
Re-Installed HTC Sync
which also reinstalled HTC drivers
Plugged the phone in let windows select the driver and instead of showing in device manager as Android Bootloader Interface it showed as My HTC Sync and worked first time, not sure what happened but sure glad thats finally sorted..
Rixsta really appreciate the advice...
Cheers
Hi all,
I don't know if my problem as already been solved but I didn't found anything.
At first, I have to say I installed windows 8 as principal operating system (I know, it's stupid...).
I used windows 8 without big problem since the deployment but today, after a bug, I reboot the PC and now I have just black screen with the message "operating system missing"... The system does not boot, just black screen with the message
Does anybody have an idea how I can solve this problem ?
(Sorry for my english)
you can put dev preview DVD or USB whatever you used to install.
and run the installation and then repair Windows 8 (if it detects a Windows installed). with system restore or maybe it will repair. if not you will have to refresh your win8.
also it can be (if you have more hard drives) that you aren't starting the one with Windows 8. so you can try and see in bios if thats the case. thats when i have seen this message.
Thanks for your answer.
When I run the pc, it doesn't launch anything, just the black screen. It's probably the bios but I can't do anything, just the message but I'm not allowed to do anything :-(
Sent from my HTC Sensation 4G using XDA App
Finally, the problem is quite solved.
When I have this message, by pushing ctrl+alt+suprr, if I'm enough fast, I can push F12 and choose wich part I want to run. Then I placed my W7 backup on CD and runned it.
It was not easy but W7 is successfull restored.
Of course, all my personal data were deleted...
But whe I reboot the PC, I've always the message "missing operating system", then I have to ctrl+alt+suprr and after F12, and then choose the hard drive, and the PC W7 boot.
It's not yet perfect but for the moment the PC works...
Thats exactly i told you. of course it changes between bios and motherboard. your problem is not your windows. its the priority of your harddrive.
I dont know what motherboard you have.
so i will find pictures to explain what you have to look for. because you didnt have to repair your Windows if thats the case. the problem its (like i mentioned) your harddrive priority.
so you go to your bios and look for the Boot section.
http://www.motherboards-reviews.com...ges/ASUS_M2N68-AM_PLUS_BIOS_boot_settings.jpg
if you go to Boot Device Priority, you can check if your harddrive is second (the one with your OS) and if you want your cd or usb to boot first if not you can leave it first.
http://motherboards-reviews.com/ASU...s/ASUS_M4N78-AM_BIOS_Boot_Device_Priority.jpg
something like this.
and if that part is right you have to go to Hard disk drives
http://www.laptops-battery.co.uk/images/maintain/bios-boot-hard-disk-drives-445x261.jpg
so there you have to check if your harddrive is first or the correct one. and ready... its probably this Hard disk devices thing. and then you don't have to use that method of changing manually which boots
Thanks for your help
I'm not at home for the moment. I'll try your method tomorrow or wednesday, I'll let you know, but thank you for the time you spent on my problem.
Sent from my HTC Sensation 4G using XDA App
Following the steps from the thread http://forum.xda-developers.com/showthread.php?p=24124828#post24124828, I lost my device on fastboot command (I followed correctly all the steps).
The device freezes on the startup screen and the PC can't recognize it properly. So the next fastboot command stays awaiting the device indefinetly.
The Android ADB Interface still remains untouchable on devices panel, but as an unspecified device. So, Windows doesn't mount the internal storage and consequently it is apparently impossible to change the damages.
Does anyone know something that can be useful?
install the correct drivers for fastboot and go ahead:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
i had the same problem
used this link helped get my device up again
http://forum.xda-developers.com/showthread.php?t=1422832
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app
o82239 said:
try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE
ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Sent from my Nexus 7 using xda app-developers app
:-/
Is there any justice for me in this bad bad world of octa-core processors and Razer Edge!!! :'(
ansh360 said:
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE
Click to expand...
Click to collapse
??? It worked and it doesn't work ???
What worked?
Try to delete the precompiled inf-file 'C:\WINDOWS\inf\wpdmtp.pnf', edit the 'C:\WINDOWS\inf\wpdmtp.inf' (see link in the post in the top...), open the XP device-manager, right-click in the yellow '!' and 'update driver'...
twics said:
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Click to expand...
Click to collapse
Do you have edit the 'C:\WINDOWS\inf\wpdmtp.inf'?
Sent from my Nexus 7 using xda app-developers app
I had a lot of problems myself getting Windows XP to work with my Nexus 7 as well... eventually I discovered that installing the latest version of Windows Media Player fixed the problem.
I wrote up a post on this issue on another forum (Sorry, XDA - this was before I discovered you guys), back in December of last year.
Anyway, here is my original post...
http://www.nexus7nexus10.com/forum/nexus-7-help/2600-cannot-connect-pc-2.html#post36608
(Actually, this whole thread is worth reading.)
The only nuisance factor is having to remember to re-enable USB debugging (Titanium Backup needs USB debugging enabled, and complains if itsn't) AFTER I've run some MTP Windows XP related file backups (USB debugging needs to be disabled, or MTP won't work)...
....or at least that is my experience.
Hope this is of some use.
Rgrds,
Ged.
Hello guys,
I have the same issue on windows XP with Nexus 7. I tried everything what was suggested and nothing is working.
I have Windows XP SP3 with WMP11 and MTP porting kit installed as well. the device is recognized and driver is instaled fine. But it's not visible on "my computer" in MTP mode. I tried to turn on usb debugging and still device is invisible in windows explorer, the same is when usb debugging is turoned off.
When device is in PTP mode it appears in "my computer" and i'm able to browse it and see all pictures and photos.
How can i browse my device in MTP mode and copy files there? Please reply if anybody knows what to do to fix this issue.
Thank you.
ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.
Taowtp said:
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.
Click to expand...
Click to collapse
The above workaround was spot on, thanks
Hello all! I have a metro PCS branded LG Leon phone with some critical data in the QuickMemo+ LG app I need to recover from internal memory hopefully without having to install a new screen. The data is located in /data/data/[some path]
I can get the phone connected to my windows 7 PC in MPT mode. I can view lots of folders in internal memory. I can't SEE the /data/ folder but I can access it from the path - however it's empty, and I cannot get to /data/data or /data/[the app path] from the windows file explorer.
If I power on and hold power and vol - at the same time, I get a factory reset screen on the phone which I can manipulate with the vol and pwr buttons - but the phone is not recognized on the PC via USB in this mode. If I hold VOL + and plug in the USB with the phone off, I get some distorted command prompt stuff, then it goes in to Firmware Update. In this mode, it is detected by the computer, but shows in device manager with a ! - and the error is error 10 - Device Can Not Start.
ADB and Fastboot both always show no devices connected no matter what I try
If I can figure out a way to get this sucker seen by ADB I'm golden... if I can get fastboot to see it I think I have a process by which I can get in to what I need...
Why can't I get either program to see this sucker?
Or should I try my Linux box running Ubuntu?
Also - as I sit here and type, with the phone plugged in and showing FIRMWARE UPDATE [where I had the error 10 before] I tried switching drivers to just the plaIn MTP driver. No luck initially, but all of the sudden I hear the windows Bedoop new device sound, and drivers installed, and I no longer have the error 10 in device manager.. however I still cant see the sucker in ADB/Fastboot.
Help!
-Marky