Hello,
Not sure if anyone has had this issue or not.
I used the galaxy nexus toolkit 7 to unlock my bootloader so that I could install the jellybean update, which seems to be working great. My problem now is that after unlocking and rebooting the phone, windows 7 found the phone as new hardware, shows up as just galaxy nexus in device manager, and the toolkit won't detect the phone in adb mode, even though auto run pops up and I can still copy files to it.
I need the toolkit so I can restore this .bak file of all my apps back to the phone. Unless there's another way to open this .bak file? I suspect that gnex toolkit won't see the phone because I can't choose jellybean from the build list?
Help is appreciated.
Figured it out
Sorry guys,
USB debugging got turned off when I installed jellybean. Now that it's on, the toolkit detects it, and the restore is working.
not so simple for me
I turned on USB debugging, and Toolkit appears to do its thing. I even get the screen asking me for a password. Android tells me that it's starting to restore the backup, then immediately says that the backup ended. Nothing changes: no apps, no settings. help!
Related
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
ex-googler said:
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
Click to expand...
Click to collapse
have you tried manually flashing the stock signed by google rom through your stock recovery yet? it sounds like it got corrupted or has some corrupted data. id try to manually flash it.
aliiasgar said:
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
Click to expand...
Click to collapse
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
ex-googler said:
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
Click to expand...
Click to collapse
you need the nexus s drivers go to the pdanet website http://junefabrics.com/android/ and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
simms22 said:
you need the nexus s drivers go to the pdanet website and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
Click to expand...
Click to collapse
I've already installed that. It won't detect the phone properly because I can't enable the USB thing within the android OS since I'm blocked from fully loading up the phone.
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's interesting you say that because I do notice an error during recovery and selecting data wipe. I had a colleague in the android dept tell me it's most likely bad flash memory.
"E:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata"
I'm gonna call Samsung tomorrow.
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
i've had a few issues with this on my Droid Pro. with windows connection a connection assistant came up with some options that I was able to get it to work as a drive.
Getting it to work with adb is another issue alone. The phone needs to be in "debug" mode. I would search for a tutorial on this because you need to edit files on the computer.
for example on my windows I needed to edit one set of files, while on my linux I had to edit another set of things.
I leave my phone in debug mode because i use it for my android app dev on both computers. try that and see if it shows up on your mac.
So here's everything I've done to the Asus Memopad HD7 (me173x) with Android version 4.2.2 ever since I got it (in the span of a few months):
rooted the device using Framaroot.
deleted bloatware that came with the device.
noticed that there's an update to version 4.2.4.
couldn't install update because I deleted some of the system apps.
used a root explorer app and the zip here to paste the missing APK files, I also switched the current build.prop file with the one in the downloaded zip (thought that it also changed while deleting the bloatware).
unrooted the device.
rebooted the tablet into Recovery.
wiped data.
I thought it would bring the tablet to a sort of "out of the box" shape but now it's stuck in a boot loop and I don't know if the situation is still reversable. I can still access Recovery.
I tried using this guide for help however ADB cannot detect my me173x. It does detect my i9100 when booted to recovery and connected though..
When I connect the tablet and power it on the PC does detect it as an unspecified device named "me173x".. Looking through Device Manager it reads MTP USB device..
Can something still be done about it? Or did I just brick my tablet?
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
donk165 said:
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
Click to expand...
Click to collapse
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Mr hOaX said:
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Click to expand...
Click to collapse
Fair enough, well i'm thinking I may move back to CM11S if things don't work out on Blisspop. If I turn off USB debugging and then switch to camera (PTP) mode and then back to MTP mode, my phone then connects fine. I wanted it to connect so I could copy my Titanium backup files off the phone and onto the PC. In the end, my mate told me about Airdroid and I managed to download them through that as a ZIP file. For some reason, the titanium backup folder isn't visible from your computer, I tried copying it to the DCIM folder and it just gave me a 1kb file. I also tried a new folder called backups and it was empty when I looked on my PC, but the files were visible when using Airdroid and also when I used a file browser on my phone.
Weird stuff!
Just wanted to bump this and see if anyone has a solution or even just an explanation.
Whenever I plug my OPO into my PC (with the original cable), the device, A0001 is found but is shown in Device Manager with an exclamation point. If I then right click on it and chose uninstall, and then reconnect the phone, it will connect and work fine for MTP/PTP modes. If I put USB debugging on, the MTP doesn't always work after. But no matter what, if I shutdown my PC, and then come to connect the phone the next day etc, I have to do the uninstall of the driver then reconnect for MTP to work. Pretty frustrating!
Anyone know why the phone isn't remembered by my PC correctly? I'm on Windows 7 x64 if that means anything.
I'm moving back to stock ROM soon so I'll see then if its something to do with the unlocked bootloader or using a custom ROM. I'll report back if I have any luck
Bumping this again, its still the same on 6.0. I don't fancy moving back to stock ROM, I like CM over Cyanogen OS, but this problem is really frustrating. Every single time I connect the phone to the PC, it will come up as A0001 but with an exclamation mark next to it in Device Manager, if I right click and uninstall the driver, then reconnect the phone, it works fine then. But if I restart my PC, it does the same thing where it cant find the right driver for the phone.
Is there anything I can try to fix this?
I'm at a point where i need enough help that im starting a thread about it.
How it started:
It all started when i restarted my G5 with Quick Reboot [ROOT] (AntaresOne Studio ) because it was lagging/slow.
After restarting the phone would not boot. It would always go to the Optimizing XXX of XXX apps, finish, restart and optimize again.
What ive tried:
I factory reset my G5 by using TWRP and formatting the data partition.
That allows me to use the stock? G5 ROM, but one huge issue, is that if i turn on Wifi, the phone reboots within 2 seconds to the tmobile screen and gets stuck.
It fails to reboot after that.
My phone has retained root. I was able to verify that by downloading Root Checker and it confirmed that i have root.
SuperSU also worked properly and SnapChat fails to login because it is detecting that i still have root.
I have been rooted for several weeks without any problems fyi. I have not updated my phone at all.
I was hoping i could unroot and flash the stock unmodified? tmobile ROM,
but in download mode, LGUP detects the device as "unknown device"
and if the phone is booted, LGUP does not detect it, instead it gives me a drivers need to be installed warning.
(The drivers are already installed, because i installed then when originally rooting, i also reinstalled everything the root guide suggested anyways)
At this point i am clueless as to what else i can do.
Currently i can use the phone more or less fine but i can only run on data.
Play store has trouble installing apps via data so i tend to download and install APKs directly via file manager.
Thank you for any help and insights in advance.
Well, I would suggest flashing the 10D kdz to get back to stock. However you need LGUP working to do that...
It sounds like a driver issue... I would uninstall the driver, reboot, reinstall, and try again.
As for uninstalling the drivers, that is easier said than done sometimes. You may need to manually remove the driver files if the uninstaller does not.
You may want to use something like Revo Uninstaller to monitor the install and then do an uninstall again.
If you have another computer, doing it on that computer could be an easier route, heh.
http://imgur.com/a/HIy8z
SO i tried it on my mom's windows 7 desktop, and it look slike all the drivers installed properly, however when i run LGUP, same thing happens.
It shows up as "unknown device". The other LG software also doesn't detect it. I can factory reset the phone and it stays rooted, but the broken wifi is a huge issue.
I'll keep try thou. Your driver issue idea seems valid but idk what is happening at this point :/ I used to love this phone and LG (coming from the S4) but no so much anymore...
The chinese brands will take over at this rate lol. Axon 7 is compelling. Again, Thanks for the advice
EDIT:
I fixed it. Issue was due to build.prop. because the file was modified it caused the software to not detect the phone properly apparently, so putting back a clean stock build.prop allowed LGUP to recognize the device.