Develop Bugs

Questions regarding various stuff.

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.

[Q] Use computer to turn phone on?

So short story, my galaxy nexus's power button doesnt work anymore. It stopped working for no reason yesterday, yet when I plug it into the charger the charging screen comese on. I want to be able to power my phone on so that I can get all the information onto my computer so that I can easily transfer stuff to my new phone (replacement gnex coming tomorrow) Is there a way I can turn on my phone without using the power button? Any help would be much appreciated.

If you've got the SDK or just ADB available, you should be able to use the command of "adb reboot" to get the device to boot up. Could be wrong.

Can someone guide me in the direction I need so I can do this adb reboot?

chantheman525 said:
Can someone guide me in the direction I need so I can do this adb reboot?
Click to expand...
Click to collapse
Download the ADB file (usually bundled with Fastboot) from any one of these guides that requires it. Or just Google for it.
Unzip all of that, use command line to get into it's directory, hook your phone up over USB, and type:
Code:
adb reboot
Again, not sure if this will work when the phone is off. If it will work, I think you had to have USB debugging turned on. Its not working for me currently on OSX. So I don't think it will. Maybe there's a different ADB command that can help you.
Its a long shot. There are probably better options.

I'd agree with adb reboot if your computer will recognize it from this mode...
Use the guide linked in my sig to set up ADB if you need.

I'm a newbie to all this, but I don't think anyone here mentioned the necessary step of downloading and installing your phone's specific ADB drivers to your computer.
So, to recap:
Download your phone's ADB drivers on to your computer and install them.
Plug your phone in.
Go to your command prompt and type 'adb reboot'.
I think. I'm new, as you can see by my post count and thanks meter.

I tried to adb reboot. Unfortunately the galaxy nexus cant be recognized when the phone is off. Disappointing but not the end of the world. Thanks for everyones help.

If adb works in download mode you could make a jig to get you there.
Sent from my Galaxy Nexus using Tapatalk

[Q] How do I mount internal storage from recovery mode?

I have a problem. I have been passed a HTC Wildfire that has a big chunk missing, namely the touchy part of the screen On this phone is, apparently a photograph that I need to rescue or the world is going to end. The phone is configured to charge only when connected to a computer so I need to access the internal storage, whilst in recovery/fastboot and save the photo.
I have HTC Sync installed, the SDK too, but when I use ADB to list devices I see nothing.
Can anyone please point me in the right direction?

philskents said:
I have a problem. I have been passed a HTC Wildfire that has a big chunk missing, namely the touchy part of the screen On this phone is, apparently a photograph that I need to rescue or the world is going to end. The phone is configured to charge only when connected to a computer so I need to access the internal storage, whilst in recovery/fastboot and save the photo.
I have HTC Sync installed, the SDK too, but when I use ADB to list devices I see nothing.
Can anyone please point me in the right direction?
Click to expand...
Click to collapse
How did you save a photo on the internal storage?
More on topic:
If you know where it is you can use adb to pull it out.
Command to do this is:
"adb pull [location of file here]"
If you don't and you know the name, you can use the shell to "search for it"
command:
adb shell
now that your in the shell, use ls to list what's in the folder and cd [folder] to change the directory.

Thanks for your speedy reply!
It's not my phone, so I have no clue how a photo got on to the internal storage. Your response was very helpful, but at the moment I cannot get the device to list in "adb devices". Can you shed any light on that?

Try to turn it on and see if the trackball still works.
If it does, navigate to settings->applications->debugging and turn on USB debugging.

My apologies, I have just noticed I have posted this in the wrong forum. It is a Wildfire S not a Wildfire (no trackball). I will repost in the correct forum.

I did find another way...
but it requires you to install Ubuntu.
http://forum.xda-developers.com/showthread.php?t=981774

SOLVED Stick mount...?

Ok long story short. I restored. Now no recovery. No super user. Fastboot doesn't see phone but does when in regular mode. Think somehow or another during the restore my internal was mounted/un mounted or however that goes because I'm seeing files/folders within my phone that aren't there and won't let me remove because "a device is missing from the network". A folder named windows and one named edited appear when I'm connected to computer but not when i disconnect. How do i m mount/unmount so phone is read correctly? Adb works fine.
I am current and up to date with the sdk and drivers. I have fastboot installed. I know how to use it, please skip the referrals/how-to because that isn't the issue.
Spawn The Dark Ages

JediNinjafication said:
Ok long story short. I restored. Now no recovery. No super user. Fastboot doesn't see phone but does when in regular mode. Think somehow or another during the restore my internal was mounted/un mounted or however that goes because I'm seeing files/folders within my phone that aren't there and won't let me remove because "a device is missing from the network". A folder named windows and one named edited appear when I'm connected to computer but not when i disconnect. How do i m mount/unmount so phone is read correctly? Adb works fine.
Spawn The Dark Ages
Click to expand...
Click to collapse
As for fastboot, sounds like you need to get the proper driver. It's a different interface than adb. Try the naked driver efrant links to in his 101 FAQ post.
As for the other issue, I'm not sure I follow. Using a file manager on the device, you see files/folder that "aren't there" and via adb shell you don't see them? Please elaborate.

Ok. When i attach phone to computer, my devices lists mtp device (galaxy) under portable devices and Android debug interface under Samsung phones. the window that asks what would you like to do pops up and i choose view files. There were "windows" and "edited" folders that i don't know where they came from. If i click the windows, it will list some of the pics i have on my external drive. If i dismount my external..those folders will say device not attached to network. If i plug phone in without external at all..those folders do not show up in my phones sdcard.
When i open adb from sdk/platform tools that has the fastboot driver while phone is in this strange interface and adb reboot-bootloader my phone reboots but fastboot doesn't see it and both of the adb interface and mtp device disappear and are replaced with Android 1.0 with best driver installed. since it said Android debug while on, i rebooted, did adb devices then for kicks fastboot devices and got the message fastboot does not work with production devices...meaning basically because the Android system is running. So, i.think something had been mounted/dismounted and that's why my drivers are installing backwards
Spawn The Dark Ages

I saw a thread on gto (?) And stick mount and it seems that my phone is mounting as if i had those programs. Which i don't and never had.
Spawn The Dark Ages

JediNinjafication said:
Ok. When i attach phone to computer, my devices lists mtp device (galaxy) under portable devices and Android debug interface under Samsung phones. the window that asks what would you like to do pops up and i choose view files. There were "windows" and "edited" folders that i don't know where they came from. If i click the windows, it will list some of the pics i have on my external drive. If i dismount my external..those folders will say device not attached to network. If i plug phone in without external at all..those folders do not show up in my phones sdcard.
Click to expand...
Click to collapse
What do you mean by external? The gnex doesn't have an external SD. Forget browsing the /sdcard with Window explorer at this moment, let's try more robust ways first. What do you see using a file manager on your device? What do you see using adb shell? (type ls -l)
When i open adb from sdk/platform tools that has the fastboot driver while phone is in this strange interface and adb reboot-bootloader my phone reboots but fastboot doesn't see it and both of the adb interface and mtp device disappear and are replaced with Android 1.0 with best driver installed.
Click to expand...
Click to collapse
Yes, the adb interface device and mtp device are gone because when you are booted in bootloader the phone uses another interface (fasboot). I'm sure it says best driver installed, but if 'fastboot devices' doesn't list your device I beg to differ that's true. Manually update the driver using the naked driver version 0.7: http://forum.xda-developers.com/showthread.php?t=1379875
since it said Android debug while on, i rebooted, did adb devices then for kicks fastboot devices and got the message fastboot does not work with production devices...meaning basically because the Android system is running. So, i.think something had been mounted/dismounted and that's why my drivers are installing backwards
Click to expand...
Click to collapse
Fastboot won't work if you're booted into Android OS. Again, it's an interface of the bootloader.

Oh..i just remembered..when i did have root, i had a program that would tell me system info and it listed internal memory and sdmemory. This was just before i restored.
Spawn The Dark Ages

My external harddrive for my computer. I know all this you just said hence i posted the thread
Spawn The Dark Ages

JediNinjafication said:
I saw a thread on gto (?) And stick mount and it seems that my phone is mounting as if i had those programs. Which i don't and never had.
Spawn The Dark Ages
Click to expand...
Click to collapse
Afaik, stick mount is an app that allows you to mount USB thumb drives with your gnex. If you don't have one of those attached and you never used this program, I doubt it's the cause or your problem.

This is not my first Android. each time i post everyone immediately refers me to a toolkit or how to on the sdk. Let's skip all that, assume I'm current and up to date and know how to use it. Now, read the post and continue from there. Not trying to be *****y, but this check drivers and fastboot banter will continue three pages.
Spawn The Dark Ages

And that's why I'm asking because that's how my phone is mounting.
Spawn The Dark Ages

I didn't refer to a toolkit or sdk. And from your post, I doubt you understand the difference between fastboot and adb, otherwise you would know trying 'fastboot devices' while Android is booted doesn't make any sense.
Either way, I don't respond well to commands when I'm just trying to help. Good luck solving this, but it will be without me.

Petrovski80 said:
I didn't refer to a toolkit or sdk. And from your post, I doubt you understand the difference between fastboot and adb, otherwise you would know trying 'fastboot devices' while Android is booted doesn't make any sense.
Either way, I don't respond well to commands when I'm just trying to help. Good luck solving this, but it will be without me.
Click to expand...
Click to collapse
If you read what i posted...you would see that i said "for kicks" i tried fadtboot and it didn't work obviously because Android was running.
Spawn The Dark Ages

Nor was there any command issued. It was a request to skip the usual fastboot/adb and get down to the issue...saving each one if us typing and time.
The time spent explaining i am current and up to date with everything is horrible. Only reason i did the fastboot is because i have never seen it say Android debug interface while my phone is powered on...only when it's in fastboot. Nor have i ever had it sharing files with my external hard drive...like it were stick mounted.
Spawn The Dark Ages

Spawn The Dark Ages

JediNinjafication said:
If you read what i posted...you would see that i said "for kicks" i tried fadtboot and it didn't work obviously because Android was running.
Spawn The Dark Ages
Click to expand...
Click to collapse
You obviously think you understand what you are doing, but it us clear to everyone but you that you do not. I'm not trying to be mean here, but you are not listen to everyone who has tried to help you. I have tried in your other thread, petrovski80 tried in this one, and others in your other threads that you keep creating. One: you do not have the fastboot driver installed. Period. Two: to answer your question in your other thread, once you do install the fastboot driver, you can follow any one of the multiple guides on how to get root. Three: do not trust what you see in mtp on windows - it is not refreshed properly often. Four: no matter how many android devices you have had and have rooted and no matter how many drivers you have installed in the past, you still have not done the things you need for the GNex.
Sent from my Galaxy Nexus using Tapatalk 2

http://forum.xda-developers.com/showthread.php?p=30778314#post30778314

JediNinjafication said:
http://forum.xda-developers.com/showthread.php?p=30778314#post30778314
Click to expand...
Click to collapse
Funny, because no one suggested you use the driver that came with the SDK. If you look up to post #5, you would have seen that the driver that was linked to was the one that you should have used, and you would not have had to make any changes to any setup.inf files, and your issue would have been solved a while ago.

Funny because I had multiple different ones put in my dropboxthat didn't work either. Point being the drivers were there.
And I learned something new. Win/win

Broken Screen/Digitizer need backup

Dropped phone, broken screen/digitizer, doesn't respond to touch
Was able to see the screen a bit yesterday but now its almost all black. I mainly just need my photos off it. Tried an RMA to replace the screen but they said they had to wipe everything first
Is there any way I can pull the photos off it? I haven't tried an otg yet, but I also can't see the screen, so im not sure it would help
Is there a screen sharing program I could get w/o first installing it on my phone?
I think my phone may be rooted, i forget if i ever did, but i dont have TWRP installed on it? (i dont super know what that is but i see other people talking about it)
Any thoughts on how to pull photos off it? I tried the adb devices but the cmd prompt doesn't seem to recognize the phone
Im quite sure I have debugging enabled, just coudln't get the file transfer button hit

Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk

Explorer23 said:
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Ok cool, how would i go about sorting the drivers? o.0

jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
side note.... wth is this image verification lol, ive tried like 30 of them, why is it so hard to post lol ><
Click to expand...
Click to collapse
Sorry, can't give definite answer, I know that I had an issue with drivers (device wasn't properly recognized) and tried pretty much everything that Google suggested ... Until it finally started working. I have no idea exactly what solved the issue, it was over a year and a half ago. The next time I clean installed Windows (10 in both cases) it was smart enough to automatically find right drivers.
So ... I'm guessing Googling something like "OnePlus 3 Windows # drivers" should find something useful?
About image verification: are you talking about anti-bot system that checks if you're human? Wouldn't know much about that, never personally had issues with it, but also very rarely see it on XDA as I'm nearly always checking this forum in Tapatalk app.
Sent from my OnePlus 3 using Tapatalk

jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
Click to expand...
Click to collapse
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.

tnsmani said:
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
Click to expand...
Click to collapse
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works

Had the same issue with my Lenovo P2. Only i didn't have debugging enabled. If you have, screen mirroring should be an easy solution. You could just see ur phone screen on ur computer that way. What helped me was to forceboot the phone to recovery with the hardware buttons, then connect it to ur pc. TWRP will automatically launch MTP. When u backed up evrything, you can wipe ur device through adb

jsaden said:
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Click to expand...
Click to collapse
I don't know about Win 7. It will work on Win 10. Most likely, this should not be needed in Win 7 at all as the drivers should install whether signed or not.
Regarding copying data, a simple command of "adb pull /sdcard" will copy all the folders, files, data etc to your PC. You can also specify where you want the data copied to, simply add the path to the command above. This will work whether your screen works or not. Of course, there are other methods of copying data, you can search for it if you need it.