Related
I have an extreme problem with my Nexus. I've been through thick and thin with this phone, and I'm hoping you guys will help with a solution to this problem.
The power button to my Nexus is broken completely. I stabbed it so much that the clicking black part is completely removed from the slot (on the motherboard).
One time, my Nexus S died, and I realized I had no way to turn it back on. I tried every single method (battery pulling, button pressing, USB connecting, etc) with no answer. I finally was able to find a solution. I used Odin to restore the bootloader tar md5 file, and thus auto rebooting the nexus (when the box is checked). This worked like a charm, until I realize I made a fatal mistake.
I chose an md5 file for the ORIGINAL Nexus S (not 4g).
I was able to easily go into recovery with Quick Boot from the Play Store. I installed Raspbean Jellybean (02-05-13 build), but the installation was very faulty. The home button is nonfunctional (it vibrates when pressed, but nothing happens) and Browser is not working as it just closes itself instantly. Like an idiot, I didn't install Gapps before rebooting into the ROM.
Stuck in that dilemma, I used the built in email app to sync my Gmail account to the phone. I sent a Quick Boot APK to myself to try and open so I could reach recovery, but it said there's no type of program that can open that file (maybe because Gapps isn't installed).
The last thing I tried was Odin again. I tried to restore the ICS release keys, but Odin will not recognize my phone anymore for nothing. I tried 3 different USBs (2 with shorts, and 1 normal one. I don't know if the type of USB has anything to do with it). Nothing.
So here I am with a faulty, Gappless ROM on my Nexus S 4G with a completely broken power.
I'm wondering if you guys have any solution/suggestion to get Odin to recognize my phone again so I can restore it and work from there.
Apart from that, ANY solution to this problem is highly acceptable and greatly appreciated (ways to get into recovery, etc). I don't want this to be the last of me and my sweet ole Nexus =(,
Thanks x1000 XDA!
Hey Guys. I was actually able to reach recovery, because the ROM I'm using has a Power Menu widget in it's quick settings (Go Figure). But my phone is still unable to be recognized by Odin in Download mode. The phone is also not recognized by my pc at all. It only charges, no matter what USB I try. I even tried mounting in recovery, no go.
Please help. Thanks!
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Wow - you're in a difficult situation...
You being on stock I can only imagine the bootloop is caused by something you installed.
So if you can access settings and are able to uninstall apps, just keep doing it until you are back to the original stock setup.
Are you sure the files you are trying to save are still on the SD card? Don't know how you flashed 10.6.1.14.8, but flashing a complete firmware package ususally erases /data - although your persisiting bootloop indicates it didn't...... if the bootloop is caused by an app. And I can't imagine what else would cause it.
You could try to do a factory reset in Backup&Restore but you will loose the contents of your /data partition...
You can flash the 10.6.1.14.10 firmware file, but most likely you will also loose your data.
The only way I can think of to replace your bootloader and firmware without data loss is if you try to find a copy of the 10.6.1.14.10 dlpkgfile. That is the OTA update file Asus pushes out to users. It's a patch file, meaning it only replaces/updates new files and leaves everything else alone.
If you find the dlpkgfile on some forum you would have to place it into your /cache directory and reboot - and I don't know if you can copy it to your tablet before it bootloops again.
Unfortunately the reason for your bootloop is probably an app on the same partiton with the data you don't want to loose. Unless you manage to uninstall the culprit I don't see much hope....
Good luck!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
_that6042401 said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
He's bootlooping..... How does he go into settings and turn on USB debugging?
I think the best option maybe to flash a stock Asus ROM from their site but that will wipe all data including those photos......
zanadoo22 said:
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Click to expand...
Click to collapse
I have not use this method but you could try.
You need a boot OS tool on your external sd and run it from your external sd so you can access to your internal sd to copy files from there. You can search on the internet and you should find more information on how to use them depending on what boot os you are using.. Good luck.
zanadoo22 said:
and I only have about 10 seconds before it freezes and restarts.
Click to expand...
Click to collapse
sbdags said:
He's bootlooping..... How does he go into settings and turn on USB debugging?
Click to expand...
Click to collapse
Preferably FAST.
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
LetMeKnow said:
You need a boot OS tool on your external sd
Click to expand...
Click to collapse
What is a boot OS tool?
_that said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
zanadoo22 said:
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
Click to expand...
Click to collapse
What Windows version do you have on your PC?
You can check your drivers in Device Manager. Open it, look for your tablet under Portable Devices and check if the driver has a yellow exclamation mark next to it. You should be able to update/install/uninstall the driver from here.
Try to find out if there is a setting in your Windows version to only allow Microsoft signed drivers and disable it.
Sent from my DROID4 using Tapatalk 2
Apparently if I transfer a large amount of files or say a single large file >4GB from my phone to the computer - the phone will freeze up.
Some times it will become responsive later but is pretty unstable since going to Chrome will usually cause it to freeze and I will have to reboot.
I have tried transferring a large amount of anime/tv shows and it will consistently freeze/lock up.
Has anyone else experienced this?
chronicrebellion said:
Apparently if I transfer a large amount of files or say a single large file >4GB from my phone to the computer - the phone will freeze up.
Some times it will become responsive later but is pretty unstable since going to Chrome will usually cause it to freeze and I will have to reboot.
I have tried transferring a large amount of anime/tv shows and it will consistently freeze/lock up.
Has anyone else experienced this?
Click to expand...
Click to collapse
first try another device to transferring from that usb port u used for phone
this problem is similar to unstable connection
and unstable connection can have different cause
ROM, micro-port, pc-port, cable, storage of phone or pc & etc
if problem solved after rebooting so it was maybe because of cache or an error in device storage
x102x96x said:
first try another device to transferring from that usb port u used for phone
this problem is similar to unstable connection
and unstable connection can have different cause
ROM, micro-port, pc-port, cable, storage of phone or pc & etc
if problem solved after rebooting so it was maybe because of cache or an error in device storage
Click to expand...
Click to collapse
it will happen when i try to transfer over WiFI to a network share using ES File Explorer (no cables) or even when i transfer to a meenova sd card reader via StickMount/USB OTG.
The problem is not often solved with rebooting..
sometimes not letting the phone sleep will allow it to continue the transfer successfully.
chronicrebellion said:
Apparently if I transfer a large amount of files or say a single large file >4GB from my phone to the computer - the phone will freeze up.
Some times it will become responsive later but is pretty unstable since going to Chrome will usually cause it to freeze and I will have to reboot.
I have tried transferring a large amount of anime/tv shows and it will consistently freeze/lock up.
Has anyone else experienced this?
Click to expand...
Click to collapse
I have the same issue. It took forever transferring photos from my PC to the N5 when i first got the phone due to constant crash and it's the same deal when I made a nandroid backup and trying to transfer to my Win8.1 PC.
I read of the same issue for some people and I wonder if there's a fix? This happens as OP said when you're trying to transfer rather large files using USB. I'm using Airdroid as an alternative, but it's VERY slow.
Anandtech review noted that at around maximum transfer speeds the phone would become unresponsive temporarily.
bblzd said:
Anandtech review noted that at around maximum transfer speeds the phone would become unresponsive temporarily.
Click to expand...
Click to collapse
so if my phone freeze, what will help?
bblzd said:
Anandtech review noted that at around maximum transfer speeds the phone would become unresponsive temporarily.
Click to expand...
Click to collapse
This is not temporary. I don't think there is a fix. I may just end up returning the phone because of this and the static on video recording.
chronicrebellion said:
it will happen when i try to transfer over WiFI to a network share using ES File Explorer (no cables) or even when i transfer to a meenova sd card reader via StickMount/USB OTG.
The problem is not often solved with rebooting..
sometimes not letting the phone sleep will allow it to continue the transfer successfully.
Click to expand...
Click to collapse
i didn't use for 4GB over wifi! (it will get lots of time!)
but ~2GB i did
there might be bug in ROM for it
anyone check this on custom rom of N5?
Same problem here, when transferring many files to my Nexus 5, after a few moment the file transfer freezes... Wonder if there is any fix for it
Harvin Dhillon said:
Same problem here, when transferring many files to my Nexus 5, after a few moment the file transfer freezes... Wonder if there is any fix for it
Click to expand...
Click to collapse
Huh, so I'm not going crazy. Now the better question is whether or not it's better that I'm not alone in having my My Nexus 5 hang on file transfers. I use FolderSync to keep my all of my Android devices sync'd/backed up to network shares/webdav over WiFi, and the remainder of my devices work beautifully, and the Nexus 5 locked up nightly until I disabled the sync.
What transfer speeds are you getting? Anandtech noted very high transfer speeds (about 150mbps) was causing the phone to lock up in their tests.
Sent from my Nexus 5 using Tapatalk
This problems still occours even on Android M 6.0 Marshmallow.
nexus 5 is a beta product. I have no doubt about it.
One thing that seems to avoid the freeze up, is first copying from the phone to the PC and latter deleting the contents, instead of cutting and pasting.
I had a 3.95GB file on my Nexus 5 and transferring using MTP to my PC kept freezing the phone. Tried different cables and different computers, but no luck. Out of desperation, because I really needed this file (it's for a project), I put the phone on airplane mode, and then tried the transfer again. It worked! I have no idea if I just got lucky. My thinking was that putting the phone in airplane mode would turn off all the wifi and cellular data transfers that might happen in the background as well as stopping or putting to sleep some Android services. Again, I don't know if this is a real fix or if I just got lucky. Just thought I would share my result.
Airplane mode didn't work (at least not by itself), so I tried rebooting into Safe Mode. You hold the power button, and when "Power Off" shows up on screen, you press and hold it instead of just tapping it. Then it will show the option to boot in Safe Mode.
Hi, I'll explain my problem quick. a week ago my Nexus 5 rebooted for no reason, upon rebooting I noticed something weird: app data configurations (app data not belonging to the user accesible memory) were all reset, it was like all apps had been freshly installed but left my pictures music and those things untouched. Wifi was working perfectly fine at this point, some form of data corruption I guess. Upon manually rebooting hoping it would come back to normal I found out wifi was behaving strangely, it would take a couple of seconds to turn on and off. After further reboots it stayed greyed out and didn't respond anymore.
So I began reading about the many possible causes and fixes. Tried reinstalling rom, reflashing kernel, going back to stock through flashing stock images through fastboot, rebooting, different radios. Nothing helped, so I decided to go a bit further and mess with the persist folder, first I checked permissions were ok and reset them anyway, then I wiped manually through a file explorer, finally I decided to do what was suggested here https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 with some success. Wifi was still greyed out after a fresh rom install but after some reboots it would pick up and work perfectly, until the next reboot. Then it didn't work anymore. I should note I backed up the files in persist through a file explorer and then manually pasted and set permissions (didn't know you could make an .img file of it) dunno if that has anything to do. They aren't corrupted it seems.
Unplugging the battery briefly fixed it for a day, then the next day the same problem came back without me doing anything.
Some more info:
-I have a working original EFS backup from before it crashed.
-Phone was rooted running CM11 when it happened, been using that rom for 2 years with EX kernel.
-It was a bit low on space (about 400mb left) when it happened, about 300mb were freed after it crashed. I have a hard time believing this could have caused it but maybe?
-It's global D821 16gb version
-GPS has always been wonky (if that has anything to do with it)
-IMEI and IMEID haven't changed.
-Calls and data work fine.
-When either wifi or bt work they show their correct, original addresses, only once wifi showed 02:00:00:00:00:00.
-Rebooting changes little, but powering off then waiting a few seconds and turning it on sometimes brings bt back.
-Leaving the battery unplugged almost fixed it, brought it back for some hours, went to sleep and when I woke up it was gone again.
-When performing the "e2fsck /dev/block/..." command above I wasn't prompted to fix any errors I think, output was "clean, 31/1024 files, 1125/4096 blocks" and the "make_ext4fs /dev/block/..." command reformats it without issue.
So yeah, I've tried everything save baking the mobo cause I'd rather be able to sell a semi working device than a bricked one
Any other thing I could try? Or way to check if it is indeed a hardware issue? im attaching a Liveboot log if it's of any use. Thanks beforehand.
uh I can't find the way to upload the log
how is one supposed to attach a file? im on my desktop with latest chrome
Currently running stock rooted 8.0 with the most current updates. Searching the web turns up a number of references to this with no real solution, searching here found no references to it at all unless I suck at searching.
I've noticed I have a lot of trouble transferring files to my Pixel from my computer (Windows 8.1). My phone is recognized, but accessing it tends to be very slow, and if you copy anything to it, it tends to stall, often before it even begins to transfer (calculating space required, etc) even with small files. Even just creating a new folder has hung it up before. I've tried different cables, different ports, and no change. Disconnecting and reconnecting the phone will get it working again briefly, but it's not long before the problem returns.
On a whim, I booted in to TWRP, and tried copying files there. First try, everything is immediately recognized, and is transferring at full speed. I just finished a 7.5 GB file transfer with no issue, after transferring a 3.5 GB right before successfully. The good news is this seems to be a viable workaround for now, but it'd be nice to not have to boot into TWRP every time I want to transfer something. Anyone else having this problem or have a solution?