Hello people of the tech world,
Im going spastic over here trying to install Lineage OS on my Xperia.
I looked into 'wiki.lineageos' and 'android geek' and followed the steps....
I have unlocked bootloader, got the code, unlocked oem, downloaded ADB fastboot package (platform tools) from lineage website and (two other websites later on just in case there was a difference), I opened PowerShell from the folder where I unziped the platform tools and powershell says instead of "adb" I gotta write .\adb.... after that a whole buncha text comes out. I typed .\adb devices and it showed me a device. However after going into 'adb reboot bootloader' nothing else works, when I type 'fastboot devices' it says its waiting. When I try to add the code, it doesnt recognize anything.
My computer cmd doesnt register adb at all nor anything after that.
At this point I also have minimal a&f and I tried 15sec ADB which did nothing because it says it cannot find the path. So I tried going into Environment Variables and creating path with the copy/paste technique to the "user variable" AND "system variable" AND creating new paths in each and also paste into existing paths in each. Only thing I didnt try is to put paths everywhere in the same time! and each time I created a path I tried the 15sec adb and it kept saying theres no path.
Minimal ADB works nearly the same as PowerShell and it says the same thing.
Also in the meantime I downloaded Xperia Usb drivers and tried to install it but it has exclamation marks and atm I have no mental capacity to deal with it. It says code 10. and Im in code red >_<" .
In the device manager I see my Xperia under portable devices, and the connection between my phone and laptop works fine, even the Companion works.
Im using HP laptop, win 10 and my Xperia version is 9. Help pls.
Related
Sorry, i know you must get this all the time guys, but i'm really struggling with rooting and such.
I'm on 1.72 and have no idea how to downgrade. I know you might say "read the guide" blah blah, but i don't understand it "Moron" i hear you saying. Anyway, Is there a complete noob guide for it anywhere? Like literally one that talks you through every step?
Also, my screen cracked, so i opened it up and replaced the screen myself, didn't have insurance or the £170 to have them fix it. Before the screen cracked it was doing this thing where it looked all psychedelic, Whites have blue coming off them, blacks have reds coming off them, that kind of thing. and its doing it again. This made me think it was a software issue, it happen to anybody else? I was thinking if i put a different rom on it, it'd stop, but i dunno. Anyway, thanks for any help anyone gives.
Does the screen replacement involve the flat ribbon cable between the screen part of the phone and the keyboard? I'm thinking it doesn't, but I'm certainly no expert. A damaged ribbon cable can cause colors to display improperly.
Nah, its attached to the screen so it was a new one.
The screen only comes with a small ribbon cable that connects to the pcb in the front half of the phone.
There is a larger ribbon cable that connects the two halves of the phone together, you can see it if you hold the phone halfway between open and closed. If this cable gets damaged, which happens easier than you may think then it can causes all sorts of things to mess up, including the colours on your display.
Unfortunately this cable is attached to the screen pcb so needs to be replaced as one unit.
So i'd need to replace my main pcb? Damn. Thanks for the help though! Could anyone help me with rooting?!
Sent from my HTC Vision using XDA App
at which point are you getting lost? sussed downgrading yet?
emdaftrave;14529179.Could anyone help me with rooting?! :D
.
Sent from my HTC Vision using XDA App[/QUOTE said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
Just have a search and there are numerous step by step guides, I was a total amateur and managed to do it, I think the hardest part to try learn would be using ABD (command prompt) and how to navigate to directories and push files but there are numerous guides on this forum so just pick your simplest and go for it!
elliott2705 said:
at which point are you getting lost? sussed downgrading yet?
Click to expand...
Click to collapse
Pretty much trying to install the sdk, i think im gonna reinstall it because its being a bit dodgy for me. But thanks for all the help guys!
Sent from my HTC Vision using XDA App
silverwind said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
can you use the SD card already in there as a gold card, or do you need a separate one?
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
emdaftrave said:
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
Click to expand...
Click to collapse
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
pmcqueen said:
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
Click to expand...
Click to collapse
ok, i've done it, thank you very much! now to just downgrade and root!
Ok so i'm using the XDA wiki guide on rooting, and i've got to the part where you move all the files onto the phone. Specifically, the files that aren't moving are:
$ adb push flash_image /data/local/tmp/
$ adb push su /sdcard/,
I'm getting a "Permission denied" error in command prompt. I also don't have an /sdcard directory on my phone, maybe thats why i'm getting an error?
EDIT: Never mind, i had the phone in Disk Drive mode when it wasn't supposed to be. Sorry for the double post.
Hi there, sorry for being another needy noob, but such is my reality. I've spent the last couple days reading and trying stuff out. A friend gave me it and I opened it up without signing into an amazon account. KFU shows offline and unknown boot status. I wasn't able to run the KFU install.bat because XP blocked it for being unsigned without any warning popup that allowed me to choose, which didn't respond to changes made in the drivers signing section. I was able to manually install by plugging it in, going into device manager, finding kindle, right click, blah blah blah. It shows that I'm in normal mode there with "Android Composite ADB Interface" but KFU still shows offline and unknown. KFU is in a c:\kfu folder as directed and I downloaded the fbmode file into a software folder within that. In the cmd prompt I copied and pasted "adb push C:\kfu\software\fbmode /data/local/tmp/" at C:\kfu\tools and get "*daemon not running. starting it now* daemon started successfully* error: device not found". Can I just drag and drop the fbmode file into a kindle folder through the windows "my computer" section where it shows as J:? Is that "/data/local/tmp/" part the file path for where I'd have dragged it in the kindle? I googled what that meant and didn't find anything I understood. Taking off that part brings up "Android Debug Bridge Version 1.0.25 and a list of commands for the program. I tried the next step in the guide without the "/data/local/tmp/fbmode" part and it made a recovery folder in my kfu folder with a fff.bin file in it. Figured I was causing a cascading **** storm and registered here to start this thread. I'm sure I'm missing something obvious but I thought the guide went from perfectly understandable to immensely complex from one step to the next. To be honest I just don't understand all the little shortenings everyone uses in posts and need specific step-by-step. Do I need to fully unlock this stock kindle with an Amazon account to put it in some sort of receptive mode? It shows a USB connected mode just fine since getting the ADB drivers installed, but now I'm stuck. Thank you so much for any help you send my way. Ben
No part of the /data partition will appear on your Windows system. You must use adb to push the fbmode file.
I think this is going to be another device driver problem. Right click on the Android Composite ADB Interface in the device manager, go to properties and take a look at the hardware IDs. You should be seeing this...
USB\VID_1949&PID_0006&REV_0216&MI_01
USB\VID_1949&PID_0006&MI_01
If those values don't match, uninstall those drivers using the directions here...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Try disconnecting and reconnecting the device and find the proper interface. The hardware IDs above must match on the interface where the device drivers get installed. That's the only way adb will be able to "talk" to the device. This might help you as well...
http://forum.xda-developers.com/showpost.php?p=26999297&postcount=37
give this a try it will rule out xp`s unsightly driver issues http://forum.xda-developers.com/showthread.php?t=1882565
Is there any reason that I can't get fastboot commands to work with W7 64bit ?
I've been using them fine for about 2 years but I think it was on a 32bit system.
Just got a new pc which is 64bit.
The drivers install but when I open a command box, in "platform tools", and type "fastboot devices" I don't get the serial number.
It's not the phone that's at fault because I get the serial number when I use a laptop running xp.
Cheers
Check your setup and ADB drivers. Also, when you run an adb command for the first time, you should see it starting the adb daemon. Make sure it is starting correctly, and that it is in the process list.
I will say that it works, because I just got my phone's serial number on my work machine, and last night I updated my N7 and old Galaxy S2, from a Windows 7 64-bit system.
jshamlet said:
Check your setup and ADB drivers. Also, when you run an adb command for the first time, you should see it starting the adb daemon. Make sure it is starting correctly, and that it is in the process list.
I will say that it works, because I just got my phone's serial number on my work machine, and last night I updated my N7 and old Galaxy S2, from a Windows 7 64-bit system.
Click to expand...
Click to collapse
Thanks for your reply but I can't work out what you mean in top paragraph. My fault, NOT yours.
Cheers
Edit... I've just remembered in the past seeing the "daemon starting" prompt, but didn't see it tonight.
10rdan said:
Thanks for your reply but I can't work out what you mean in top paragraph. My fault, NOT yours.
Cheers
Edit... I've just remembered in the past seeing the "daemon starting" prompt, but didn't see it tonight.
Click to expand...
Click to collapse
Depending on how you installed the adb driver and tools, you may need to ensure that the PATH is correct. For example, I installed my adb tools in the (unimaginatively named) c:\adb folder. I put that in the PATH by adding it to the Path line (My Computer -> Properties -> Advanced System Settings -> Advanced (tab) -> Environment Variables -> Path). If this is correct, you can run adb/fastboot from anywhere, which is helpful if you have multiple devices and keep all of their files in separate folders. I am using the "kit" adb file set, not the full developer version, so the only files in the folder are adb.exe, fastboot.exe, and a couple of adb DLLs.
The first time you run adb/fastboot, your system will check to see if the daemon is running. If it isn't, it will start it. If it starts it, you should see a line with the assigned port number. It varies, but is usually ~5000 (Mine was 5037 earlier). After that, it will just return the output of the command. You should be able to launch Task Manager and see adb.exe in the process list if everything is working.
Hi, i have acer e600 i nid help using fastboot ive read that if you try to hard reset using fastboot with command "fastboot -w" or "fastboot erase userdata" it will wipe ur internal storage.. The problem is the system is installed on my internal storage (2.50gb) idk if its the one they called emulated storage but is it safe to wipe my data because i forgot my password and i think it dont have recovery mode partition and usb debugging is unchecked.
Got ONE of the M8s to take fastboot commands.
Windows 7 64bit will only install "Microsoft approved drivers".
Got into "advanced settings" by constantly pressing f8 while pc boots. Selected "install unsigned drivers" or words to that effect.
Connected phone via usb, restarted into bootloader then fastboot. PC installed drivers from phone and got the "fastboot usb" flag.
Could then run fastboot commands and got phones serial number.
The pc will revert back to NOT installing drivers not approved by Microsoft after a reboot.
Problem I have now is that only one of the m8s "can be found", strange.
Edit....constantly pressing f8 on pc reboot takes you to "advanced options". That's where the option to install unsigned drivers is.
I just can't seem to get fastboot to see the phone...
I have a Z00AD2 with 2.19.40.22 software. USB Debugging is turned on. ADB sees the phone, both from my Ubuntu host system, and from a Windows 8.1 virtual machine. When I use "fastboot device" I just get "<waiting for device>" and when I run scripts/batch files (such as the one-click root) it hangs as well.
I'm assuming there's something very simple, and probably obvious, that I'm missing - but after 8hrs of messing with it yesterday, I'm a little fried.
Appreciate any thoughts!
This morning I installed a new Windows8.1 VM, installed the Intel drivers and adb/fastboot from the sticky page in the general forum. During adb/fastboot install, should I use the drivers provided if I've already installed the Intel version? I think I've tried both ways at this point... Plug the phone in, and it is recognized in adb. Fastboot displays "waiting for device".
I tried the one-click root batch file, and when running CheckBeforeAction.bat my phone restarts into fastboot mode, with the android opened-up on its back, and the batch file continues to "make sure 'asus android bootloader interface' installed on your computer successfully" (I'm not sure it is? I don't see any reference to it anywhere...).
If I proceed further I get the "if you see '123456789 ... fastboot' then you are ready to root" message - where is that supposed to display? On the phone's screen? Finally I hit a key and the batch file says it's rebooting my phone, and it gets stuck on <waiting for device>
Again, I'm sure I'm missing something simple; but I just can't figure what step(s) I'm missing.
Solved the problem, at least in terms of running fastboot on my virtual machine... I had only set up one device filter in VirtualBox, for the phone when it was in it's normal state. When in fastboot mode it uses a different driver, and thus needed a second device filter set up - once I did that, everything went smoothly as far as adb and fastboot functionality go. Having trouble now with flashing twrp...
I've been researching and trying to sort this out on my own for a while now. I've turned up nothing, so I figured I'd ask for some help. I'll try to provide as much information as possible here.
I was attempting to unlock and root my Razer Phone from my Windows PC. I plugged it in and had it recognized over ADB with no issue. I sent "adb reboot bootloader" to start things off. Once it was in download mode, I sent the "fastboot -i 0x1532 devices" command to make sure it was recognized. It wasn't. I checked devices manager, and sure enough, it was not picking up the Google driver that every other device I own works with. I attempted to update the driver manually by pointing it to the inf file. It gave me an error stating that the driver is not designed to work with 64-bit Windows. I found that odd, as this is the exact same driver that I've used with my other devices for this stuff. I plugged in my HTC 10, since that was nearby. It was recognized via fastboot like it always was. Same cable I was using with the Razer and everything.
I booted to Linux Mint on the same machine and tried the same stuff. It would pick up the Razer only in fastboot, but not ADB. In fastboot, I could detect it with "fastboot -i 0x1532 devices", and it showed up just fine. When I attempted to run "fastboot -i 0x1532 flashing unlock" it just gave me the fastboot command reference list. (I don't have a screenshot, but it looked like this, in case you're unsure what I am referring to.) I rebooted back to the system and double checked that I had checked "Enable OEM Unlock", and I had done that already. I double checked everything with my HTC 10, and again, it all works fine on the HTC 10. ADB and fastboot are both recognized correctly on Linux.
So armed with this information, I moved over to my Linux server. I used a different cable this time, and got a similar result. The Razer phone was recognized over ADB and I was able to get into fastboot. Once there, it was detected with the fastboot devices command. I attempted to run the unlock command, and again was presented with the fastboot reference list as before. Double checked with the HTC 10, and all was workign fine with that device.
Does anyone have any ideas, or is it possible that it's the Razer phone that's the problem? I may have access to a Mac laptop later on, and I could attempt this from there, but this is getting nuts. I don't think I've ever had this much trouble getting into a device before.
Yeah I had this as well, basically you may have the latest drivers but are missing the latest adb/Fastboot executables. Apparently they have changed a few commands in the newer one and that way of unlocking isn't in the old version. Just google for the adb/Fastboot package from the Google site, can remember the exact name but it was the first hit on Google. I just extracted the whole zip to a directory and used it right from there. The reason you are getting the help screen from Fastboot is cause for that version at least, your giving it an illegal command.
I got the same problem till I put my usb in a usb 2.0 in the back of the pc in a highlight usb port witch I read after on Asus Website that suppose to charge your phone if you turn off your pc so basically a always on usb. Also I managed to unlock and brick my device only with one cable I tried 4 cables none of them worked .so for you to keep In mind
Try different cables
Try usb 2.0
Try driver from twrp for razer phone thread that worked for me
Seems to be an ongoing issue for me on my main desktop. I grabbed my old development laptop out of the closet, booted it up, and I was able to get everything recognized and working. I tried doing some more work this morning on my desktop and noticed that I'm having driver issues elsewhere, so it seems to be an issue with this machine. I'm still not sure why the Linux installation on the same machine was exhibiting the same issue, though.