Database Info

[Q] Help with Huawei Ascend

Hey, i'm new to Android and I this is my first Android phone. I saw some stuff around about removing un-needed **** the metro puts on it so I rooted it. I wanted to try to use the Icarus mod for it found at MyAscend but whenever I ran the windows fast boot for ClockWorkMOD (yes I did turn the phone off and back on using Volume+,Send,Pwr button) and even having th phone in that mode the launcher/installer for ClockWorkMOD says <waiting for device>, I have the phone drivers installed and even tried on 2 diff pc's. I tried using the stock metro flash and still it says <waiting for device>. Then I read it said to install mods I had to clear some caches on the ClockWorkMOD version 3.0.0.x. and now when I plug it in via usb it just shows the drive is conneceted but the software that allows you to choose weather to use file transferring or install drivers doesn't come up. So I can't access my SD unless I put it in my old phone and then plug that into my laptop. Any ideas on how to fix this and get the <waiting for device> message to go away?

did back your phone up first?...go to myascend.org...this forum is dedicated to that device plenty of help there

[Q] Mount USB storage under ClockWorkmod Recovery 6.0.1.0

Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max

Use this guide to recover your device.

Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.

How did you erase everything? Was it through fastboot or CWM?

I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.

maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...

maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2

*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2

The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?

Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2

Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307

I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2

[q] help pleasee :/

hello guys, I'm Brazilian and I'm using google translator to make this post.
sorry if I posted in the wrong area.
I have a nexus s, today I went to update it and did a ****ing great, now it only connects in "fastboot mode" which is a screen with the options "REBOOT bootloader" "REBOOT" "RECOVERY" and "POWER OFF"
I try to connect it the pc but he identifies nen, indeed, but it gets even identifies as "unknown device" even doing installations of sdk, samsung drivers, already tried everything.
the model of my nexus s is the i9020
he was with ICS mod9
someone try to help me, I'm desperate because my phone is not nen to begin with.
Anyone know what else I can do?
My operating system is Windos 7 Ultimate x64, does he have any incompatibility be x64 drivers?

What's the problem exactly? Does the phone boot up? Or is it stuck in a boot loop?

jj_z1 said:
What's the problem exactly? Does the phone boot up? Or is it stuck in a boot loop?
Click to expand...
Click to collapse
hello jj_z1,
thanks for replying,
I was not really very accurate, sorry.
the thing is, he does not start the system, so this is the screen that said,
follows a link to the example, the option button ai when to start the recovery clockwork he does not identify the SD of the cell, as would be usual, you know?
every time I turn it, it is this screen of "fast boot"
do not give out

What do you mean by "update it"? OTA update or did you flash a custom ROM and/or Recovery ?
Did you install "Google USB Driver" in SDK Manager? (If install fails, run SDK Manager as Administrator.)

_android_ said:
What do you mean by "update it"? OTA update or did you flash a custom ROM and/or Recovery ?
Did you install "Google USB Driver" in SDK Manager? (If install fails, run SDK Manager as Administrator.)
Click to expand...
Click to collapse
yes google sdk already installed drivers, all right.
I was trying to install a custom rom, only nen got to copy the rom sd pro, as there appears on pc.
that's my problem, it does not mount the sd because the windows do not want to install the cell, I surely identify if he manages to come install the rom I want

Do you have this installed on your computer?
If yes, and it's configured for your nexus s then just connect your phone to your pc, go to device manager, right click on the unrecognized usb device (if that's the case), click on update driver, then choose manually and navigate to the data/drivers folder where ever you have Wug's tool installed, that should install the correct drivers for your phone. Then use the flash stock+unlock option to restore your phone to stock, then redo everything to install cwm and your custom rom of choice. That worked for me.
Good luck

jj_z1 said:
Do you have this installed on your computer?
If yes, and it's configured for your nexus s then just connect your phone to your pc, go to device manager, right click on the unrecognized usb device (if that's the case), click on update driver, then choose manually and navigate to the data/drivers folder where ever you have Wug's tool installed, that should install the correct drivers for your phone. Then use the flash stock+unlock option to restore your phone to stock, then redo everything to install cwm and your custom rom of choice. That worked for me.
Good luck
Click to expand...
Click to collapse
I had this prog, only that even installing and doing everything you said I could not install the drivers, I try to manually install and even then it is as if he could not be started (code 10) in print as it is attached, have any other explanation?
I'm already rancando hairs here, lol

eojonathan said:
I had this prog, only that even installing and doing everything you said I could not install the drivers, I try to manually install and even then it is as if he could not be started (code 10) in print as it is attached, have any other explanation?
I'm already rancando hairs here, lol
Click to expand...
Click to collapse
The only thing I can think of right now is to try using the linux tool if you have access to a linux operating system like ubuntu. From experience, getting a nexus phone recognized by your computer is easiest on a linux machine (you can use virtual box if you don't want to install ubuntu on your computer). If I can think of anything else I'll let you know, if you don't get it fixed.

jj_z1 said:
The only thing I can think of right now is to try using the linux tool if you have access to a linux operating system like ubuntu. From experience, getting a nexus phone recognized by your computer is easiest on a linux machine (you can use virtual box if you don't want to install ubuntu on your computer). If I can think of anything else I'll let you know, if you don't get it fixed.
Click to expand...
Click to collapse
ok, I'll try it and then you notice, but now I'll take a nap and later I try again, but thanks for the help.

[Q] Problem with MTP

Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John

iBlameLag said:
Hey all. Done a lot of searching and have tried a lot of solutions but I'm still having the same problem.
A friend of mine brought me her phone (AT&T HTC One X Plus) that she had soft bricked my trying to root and flash his own rom by herself. Trying to fix it, she accidentally relocked the bootloader and also wiped the recovery from the device. She said she wanted it re-rooted and CyanogenMod 10.1 installed. I told her I could do it for her. I have unlocked the bootloader through htcdev, flashed on the new recovery (using CWM v6.0.2.7) and now all I need to do is transfer the actual ROM to the phone and then install it. I can't, however, for the life of me get this phone to communicate with the computer/ADB. Fastboot recognizes it fine, I can type put the phone in fastboot mode and type 'fastboot oem get_identifier_token' and it will give me the identification number of the phone and other details, so I know it's communicating with it, but when I type 'adb devices', nothing shows up. And it's the "adb push filename.zip /sdcard/" command that I have to use. I have also tried going through the recovery and mounting the /sdcard/ and /data/ and /system/ to the computer, with no luck. Whenever I click on the "mount sd" through the recovery, the page just refreshes and puts my selection back at the top making no changes.
Whenever I plug this phone into any of my computers, all of the drivers install except for the HTC MTP driver, as seen here;
img59.imageshack.us /img59/61/driverh.png (Sorry, going to have to fix that link, can't post pictures yet)
I have plugged an HTC One into the computer and it downloads all the drivers just fine and communicates with adb. Same thing with my Note 2.
Any help would be really appreciated.
Thanks,
John
Click to expand...
Click to collapse
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.

exad said:
ADB only works when the rom is loaded with usb debugging on. It's a shell for command line direct to your phone. Furthermore, recovery does not use MTP, it uses generic mass storage device.
It seems you're not the only one having issues mounting with CWM. I don't know much about it because CWM has very little compatibility with the HTC ONEXL(This forum) whereas you seem to have the ONEXPLUS there. Different phone, but if TWRP is compatible with your phone you can try mounting using TWRP instead? I understand that at one point a specific version or set of versions perhaps(like I said, we don't use CWM much for this phone) had issues mounting so you can check to make sure you have the latest version of CWM as I am pretty sure they've since fixed the issue. If you are using the latest version, you can also try issuing "fastboot erase cache" while in bootloader/fastboot to clear cache which may fix your issue.
Good luck. For better help it may be best to post in the one x+ forum subsection.
Click to expand...
Click to collapse
Thank you, flashed over twrp and the computer recognizes it. Thanks so much for your help!

[Q] LG-P506 Fastboot Can See My Device But Won't Show The Serial Number

So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.

baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.

damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.

baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.

shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.

ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.

baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk

ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.

LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >