Hello,
this is my first thread/post on this forum, if I did anything wrong please don't be super harsh and inform me to what to do better, thanks.
So why am I asking for help anyways you may ask, well I had my old Xperia Z1 laying around here for quite a while now and wondered if I could do anything productive with it.
So I came up with the idea to install a CFW like Lineage OS or something else.
This is not my first rooted and cfw phone but the first one what gives me nightmares and a headache.
So after reading all of the nice guides how to root it and how to unlock it, nothing of them is working for me, most of the threads have missing files which I cannot find on google or other just simply won't work for me.
First of all, I have rooted my phone via KingRoot in the meantime since the other methods where not working either.
I have turned on usb-debugging and also allowed installation from unknown sources.
And there we start with the first problem, downloaded the google SDK and installed all adb things I needed, did not work, then I tried it from the official sony website, downloaded the usb-driver folder and tried to install it manually, won't work either, because the device manager always gave me error code 10 "device cannot be started", I tried different sources and even die google studio thing and everything ended up with the same result.
Same error code even when I tried to activate fastboot on my phone by pressing down the volume up button, pluging the usb cable in, and yet again the same error message for this device too.
I am using windows 10 and never had such problems before with sony devices.
I hope someone of you can help me out to find a solution, if you need any further information, just let me know.
Did you solve this?
I have the same problem
snailer said:
Did you solve this?
I have the same problem
Click to expand...
Click to collapse
This may sound stupid or ridiculous, but yes I managed to work it out and was able to install the CWF on my phone which is working perfectly fine.
Since nobody was willing to help me I just skipped the part where I wanted to post my solution but yeah, this may help you too.
So what did I do? Simply I stopped using Windows 10 for this project, I just used one of my older PC's which still had Windows 7 Ultimate on it.
I just rooted the phone via KingRoot, since it was the only solution what kinda worked out for me, then I was able to install all needed SDK, fastboot and ADB files on my PC and was able to use the ones from the Sony site itself this time and after plugin in the phone to the PC, it installed everything else what was needed for the device manager.
After that was done with no error I was finally able to unlock the phone via the command which you can find also on the Sony website.
If you find this helpful or need any extra information just let me know, maybe I can help you then. Oh and if you found out a solution for you what worked, would be nice to hear that too.
Greetz
Related
I have 2 Nexus One's. The first was rooted and I had the ADB USB driver (v3) installed on my Windows XP Pro SP3 desktop and all worked fine.
I now have a second Nexus One. I rooted it, and after turning on "USB debugging" and wanting to use it with ADB, the driver USB installed again. But now I get constant "Found New Hardware Wizard" install loops, for both phones with "USB debugging" turned on.
Every time I plug either phone in, or reboot, Windows wants to reinstall the ADB driver. Right after it completes a driver install it wants to do it again.
Solutions I've tried; I have rebooted after install, uninstalled the drivers from Device Manager, deleted the drivers manually from the registry, removed any possibly associated hidden drivers that were marked error in Device Manager, and combinations of the above in various order.
I know that USB driver install loops on Windows can happen to any type of device, not just the Nexus, but in my case it's only on the ADB driver for Nexus One.
Can anyone suggest what I can do other than what I listed to stop the ADB driver endless install loop, or what is causing it?
Thank you.
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
No, I haven't found a solution to this yet. And you are the only person here that has replied.
I did contact Google and HTC and asked for their help. But since the phone is rooted I got the expected replies from both, that rooting violates warranty so they refused to help. I was expecting that, but have heard that the occasional tech support person at Google will still offer support within reason. But not in my case.
If and when I figure this out, I'll post it here to help you out.
johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
Hi JohnG75,
Just wanted to let you know my constant ADB driver reinstalls have stopped. But unfortunately I have nothing constructive to point out as a solution. I spent hours online researching for a possible solution, and found nothing worthwhile yet. I've posted in several places and got no helpful replies other than trying System Restore and going back to a point before this happened. Of course that's hardly a guaranteed fix, plus you loose any other updates and installs you have made since then.
In my case, I left "USB debugging" turned off on my phone since I wrote you last, and the only thing that has changed system wise for me, is I have installed 2 unrelated device drivers since, and MS has pushed out a security update. So today when I turned "USB debugging" back on in the phone, it did a single device install, and it didn't repeat. So hopefully this resolves it for me.
If I were to take a guess as to what appears to have solved it in my case, I would say it was the new unrelated device driver installs. Perhaps it cleared whatever was wrong in the device driver system. So maybe if you were to install some new device driver you need, or uninstall an existing one, reboot and then reinstall that same device driver, perhaps it will clear whatever is messed up in your device drivers.
Sorry I can't be of more help, and my suggestion is only a guess based on my only recent system changes.
There is very little documented solutions to this problem out there, only lots of people that have complained about the same type of problem, with every sort of device you can think of. And the solutions documented are always specific to those exact devices.
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
I have a rooted HTC One, though the root checker says it is not currently rooted.
I am trying to get my phone back to factory settings.
When I tried to attach the phone to the computer I get error messages that say that there are not any drivers. There is another message that says that there is not Hardware ID detected.
I cant seem to find any fix when I google this. I hope I can get some direction here to fix this.
I am not a developer, just an guy who likes to play with my toys.
I have tried the basics, removing the HTC software and re installing.
I tried turning the usb debugging off and back on several times.
Thanks
zubenal said:
I have a rooted HTC One, though the root checker says it is not currently rooted.
I am trying to get my phone back to factory settings.
When I tried to attach the phone to the computer I get error messages that say that there are not any drivers. There is another message that says that there is not Hardware ID detected.
I cant seem to find any fix when I google this. I hope I can get some direction here to fix this.
I am not a developer, just an guy who likes to play with my toys.
I have tried the basics, removing the HTC software and re installing.
I tried turning the usb debugging off and back on several times.
Thanks
Click to expand...
Click to collapse
We have no way of knowing what you have done to the phone already to make it invisible to windows ... can you describe what you have already done to the phone with links to the files you used.
no hardware id
I used the instructions from the following web site of QBKING77 (I could not put the link in here because I am too new, just google "QBKING77 root htc one"
Per his instructions I used the file attached and I also loaded TWRP 2.6
I have attached the file I used.
Ok I need some help. As of right now my tab is dead, the only thing it does when powered on is loads to the Asus splash screen and that's all. I can not get it into Fastboot mode at all and Adb cant find it either. I have already tried Sp Flashtools to no avail. I have all the Vcom drivers installed, every where I searched the one driver that people talked about was the mtk6585 driver ( I think that's what it is ) , the one for me that popped up and went away really fast was a driver called CLOVERVIEW. So needless to say I cant get SP Flash tools to work, and without fastboot mode im really stuck. Ever since I first came across this site a few years back I have rooted, and put custom roms on countless devices, I would call myself an experienced flasher. Well this tab has me feeling like a real noob, I can not figure it out. So if someone can help me it would be greatly appreciated. Thank you XDA world.
Try this: http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
It worked for me.
silviu74 said:
Try this: http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
It worked for me.
Click to expand...
Click to collapse
Wont work for me. Like I said, I cant get into droidboot.
Downloading android studio and all sdk tools, hopefully something in this will help. I will post updates on any progress.
zMILWAUKEE said:
Downloading android studio and all sdk tools, hopefully something in this will help. I will post updates on any progress.
Click to expand...
Click to collapse
I just got myself into the same situation. If you can get to a point where CLOVERVIEW comes up, that can be fixed (I actually just added a howto to the general section). However, I don't know how to get out of the stuck splash screen, since it's an awkward medium between download and fastboot. I'm not even sure what I did to cause this; I had just flashed boot.img and splashscreen.img and issued a fastboot reboot-bootloader.
The device does indeed pop up in download mode for about a second while booting; doesn't seem long enough for a flash. I would really like to find out if there is any way to force this device to boot into download mode.
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
AlkaliV2 said:
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
Click to expand...
Click to collapse
So, I've been on stock until I switched over to CM12. I do have a twrp backup but apparently only did that after I moved to CM12. I have only the most basic (read basically nonexistent) understanding of ADB, and can follow directions I find online but no real knowledge as to how anything works. I also did not use wugfresh, but unlocked via ADB and rooted via chainfire. Honestly, I followed most of the direction I found on youtube via a creator called wwjoshdo (I'd link but I'm not allowed).
Otherwise that feels like the info. I didn't fiddle with my nexus until I started have battery issues and then decided to unlock/root/flash, and that was about 6 weeks ago. I'm also running what standard apps for a rooted device on CM12, flashify, cyandelta, setcpu, and, Titanium Backup. Help?
llawhsoj said:
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
Click to expand...
Click to collapse
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
RMarkwald said:
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
Click to expand...
Click to collapse
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
llawhsoj said:
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
Click to expand...
Click to collapse
So this link will get you up and running with ADB (if it isn't already working): http://forums.team-nocturnal.com/index.php?/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10-updated-9-11-2015/
These are the most common commands that are used with ADB once you get it installed. Also, an excellent way to pull a log from the command prompt: http://developer.android.com/tools/help/shell.html
Assuming you can see the device once you pass the command, "adb devices" it means you are connected but the MTP driver hasn't been loaded properly. I had to fix this by cycling Android debugging and ADB notification in developer's option until Windows was like, "Hey! There it is!" Also, MTP works properly for me when booted into TWRP so if you desperately need to transfer a file you can do it from the TWRP recovery menu.
Noob Tip/Reminder: Make sure that when you plug it in the first time you change it from 'Charge Only' to MTP and if things still seem quirky reboot Windows. It's all just a game of getting it recognized at this point.