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
First post but have been reading this forum for a long time. This be the first time I have ran across an issue that has not been covered already on this forum or really any other. So here's the issue(s):
I have a stock X5 that is stuck on the Minix boot screen. I've made no attempts at modifying this device. This happened after watching some shoddy torrents of Breaking Bad. I had been noticing significant lag with the device prior to the downloads. Nothing other than standard media, social networking and gaming apps installed......there is a task killer on the device, the name escapes me at the moment.
Here's what I've tried:
1. Unplug all external devices (keyboard, external hard drives and removed SD card) and power up. Boot issue remains.
2. Unplug (then replug) power supply and start. Boot issue remains.
3. Hold reset button with pin and power up. DROID laying down with red triangle and exclamation comes up for a minute or two then it goes to the indef boot screen.
4. Held in reset button, power button and had girlfriend plug in the device. (I had no delusions of this doing anything but it stopped the gf's nagging to get it fixed for a while. I'm an electronics tech.....apparently that is the same thing as a programmer in her eyes.)
5. I've left the boot screen on for about 48 hours. Obviously this didn't fix anything.
6. Hooking the device up to my Samsung 7.7 tab. It turns on Android debugging on my tab but I really had no idea where I was going to go once I connected the devices. I just now thought of this and am planning on exploring this option a bit more with some searches. I'm quite sure there are no guides for working with these two specific devices though.
Hooking up to a computer to deal with recovery is not an option for me. I am not in the US and access to computers (other than an Internet cafe) is not an easy task. I am going to bet this is the best fix for most though.
My tab is rooted running PAC ROM if that is worth anything. This is currently my only real option for hooking up to another device. Hope to get some ideas here.
Hmm, so no one has any ideas? If using a comp is the only way can someone post how to recover an X5?
Jammertech said:
Hmm, so no one has any ideas? If using a comp is the only way can someone post how to recover an X5?
Click to expand...
Click to collapse
In case you didn't know, there is an (un)official Minix forum. May be they can help. (link)
Also, SomeCoolTech in YouTube has done a video on how to flash Minix X7. That could also be helpful.
Thanks for the reply. I was able to find someone to let me borrow their computer. Flashed the Finless ROM and it got it running again. The thing is not running smoothly though.
I had all kinds of issues then sent it in for rma, new x5 works perfectly, that is likely your best option. could you elaborate on your specific issues I am curious?
First time poster, I apologize if this post is a mess.
I recently dropped my Droid Charge down a flight of stairs. The phone itself still seems to work - I can boot it up, it plays all the proper sounds, and my 7pm alarm even went off today (hadn't had it on to test that before), but the screen is completely dead.
I've already upgraded to a Galaxy Note 3. I had a backup with SMS Backup & Restore from April; same for my Checkbook app - these are the two apps I'm most concerned about. I'd like to get the additional data since April 22.
My Charge is rooted, though I got a lot of walkthrough to do it - I also did the root over two years ago.
I have these links in the chatlog with the friend who helped me root, if that helps at all:
http://forums.androidcentral.com/dr...charge-windows-drivers-w-direct-download.html
http://www.mediafire.com/?yn37uc4z3cx3bl6
http://rootzwiki.com/topic/10515-odinall-in-oneep4d-gingerbread-236-w-cwrimo-kernelrooted/
http://forum.xda-developers.com/showthread.php?t=1172182
Problem: USB debugging was turned off when I dropped the phone. I didn't know any better until I'd already broken the screen. I've tried MoboRobo, MyPhoneExplorer, and Samsung Kies, and nobody sees the phone. It beeps when plugged in, and with Kies the hard keys light up about ten-twenty seconds later, but that's the furthest I've gotten.
I'm willing to boot to recovery and use adb/command prompt/whatever, but I can only find these instructions for other phones, and I'm worried that if I use the wrong phone's menu instructions I'll end up wiping it instead of booting to recovery. I'm also not too clear on if ADB is a different build for different phones... this is my first time doing this.
I don't have a mini-HDMI cable but if that's the better solution I'll get my hands on one.
Any help is appreciated, thank you!
Hey guys, let me just start off by saying I have spent almost 8 hours straight today trying to figure this out and dig myself out of a hole I've created for myself, that being said, I'm going to try and be as detailed as possible so you guys know EXACTLY where I am and what I've tried. This post looks long but that's because it is. It's pretty much my entire day's worth of trouble typed out. So just bare with me and see if you guys can help me out here!
I have a T-Mobile Galaxy S4 model: SGH-M919 it has Android 4.4.2. Now on to the problem: I've had this phone for almost a year now and a few months ago I rooted it. Did a simple Youtube tutorial and used Odin to do the work and everything worked out fine. A couple months down the road (yesterday), after using the phone like a teenager, downloading apps and cluttering it up it started to slow down and not run some apps. After thinking about it I decided to factory reset it. All of my contacts, photos, and videos were backed up on Google so I thought "why not?" Well, this is where $#!% hit the fan.. being rooted then factory reset, right before the phone came online it had me answer two questions about the root. Something to the effect of "Do you want to keep root? (This option is not reversible)" I thought since I wasn't using the features I originally rooted the phone for I figured nah just get rid of the root. So the phone did its T-Mobile boot up and started the Initial setup.
Everything up to to this point was fine until I wanted to log in to my Google account during the setup. Please understand that where I am I have full 4G LTE coverage and have access to a pretty fast and sturdy wifi connection. Well, when it came to the google sign in I entered my email and password and it came up with a message reading "Can't Sign in - Can't establish a reliable connection to the server" (believe me i wish that was the only issue) so after reading that, I thought I'd try with my wifi.. nope. Same thing. Since neither my 4g or wifi worked I thought it was Google's servers so I tried again this morning, same thing. (keep in mind at this point i think my phone isn't rooted anymore.) I call the t mobile store and they give me a technical support number, so I call it and I tell them i cant sign into Google. The gentleman told me he cant do anything because he can tell my phones been rooted. Only thing he suggests is to contact Google, well, the customer care number just tells you go to google.com/support and there's nothing there about my problem.
This is where I dig my hole even deeper. I tried another factory reset and up in the top left corner i still see that root text. Even the rooted android symbol pops up before the Samsung logo or t mobile. Since I saw that I thought "ohh it just didn't get unrooted all the way." I look up ways to completely remove a root and a lot of them require plugin your phone into the computer and using Odin to flash a stock firmware on to the device. I went to plug my phone into the usb port but my computer didn't recognize the usb device, having experienced this a long time ago I searched around for the latest Samsung usb drivers and I installed those. Device still isn't recognized. Let me just note before people tell me to use MTP mode or Developer tools> usb debugging or connection mode.. The only thing that happens when plugging my phone via usb is the phone starts charging and my computer makes the trumpet noise like something is plugged in. Other than that, there is NO notification of it being plugged in. The reason i stress this is because I called Samsung technical support at this point and the guy (not gentleman) treated me like a 5 year old and ran me through all of these options after i told him I already did everything he was suggesting, including downloading Samsung Kies 3 and having it install the drivers. It does not pick up the device either.. at this point I looked up ways to remove the root without the computer. I found out you can just go into the root app "SU" or something and theres a remove root option. I jumped on that opportunity and had it removed. I restarted the phone and all the problems still persist, it even still has the root text on the top left when you factory reset it again. However now, even if you factory reset and select the option "keep root," thinking it would bring back the"SU" app it does NOT.
So lets recap. I have a phone that thinks its rooted and even appears rooted to t mobile but doesn't have any of the root apps or privileges or capabilities to fix my Google log in issue (like the host file in filemanager). And I can't re-root to get that app back because none of my 3 usb ports, 3 different usb cables (one being the cord that came with the phone), or any of the ports/cables on someone else's computer will recognize the darn thing to work on that way! I have all these issues that are supposed to fix each other but I can't do any fixing because they cancel each other out too... I'm at a dead end.
In case this isn't the right forum/website/thread/post area etc.. I have this whole message saved in Microsoft Word document so I can repost it anywhere you guys might suggest better results. Any help/advice will be much appreciated.