Related
I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.
So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.
Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.
hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.
I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.
Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.
Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.
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
XT1080 Maxx - no recovery, no factory, and no USB connection to PC
I am trying to fix my brother's XT1080 Maxx, or at least get his photos off of it. This phone is stock, as my bro is not tech savvy at all.
He went to bed one night. I am not sure if the phone tried installing an update while unplugged or what happened, but when he woke up in the morning and tried turning it on, it stuck on the droid eye screen. He tried rebooting a few times and was finally able to get to the unlock screen, but once unlocked, everything crashed, like motolauncher, gapps, acore, media, etc.
We took it to several Verizon retailers, some official stores and some authorized retailers. Everyone said they could not help.
At this point, he gave it to me to work with. I tried recovery from fastboot, but it says boot failed. After lots of turning on and off, I was able to get to the unlock screen. After pushing OK to the millions of crashes, I was able to get to the settings screen. I tried everything from clearing cache to factory resetting within the settings. Nothing would work. Anything to do with data would bring up a .media crash. The best I got was turning on the Bluetooth, but nothing useful can be done with it. I also tried NFC, but could never complete a transfer, which didn't matter because I could not get to his gallery anyway. I booted in safe mode a few times and always got the same results.
I tried every option possible to connect the phone to my computer. The USB never did a thing, no matter what driver I tried using. I downloaded all kinds of programs from these forums. The computer would not recognize it in fastboot either.
I told my bro he was screwed and tried a fastboot factory reset. All it does is boot the phone in the normal way, which either sticks on the droid eye or finally makes it to the unlock screen. At this point, I am raging mad.
I decided to disassemble the phone to see if removing the battery would somehow magically allow me to connect it to the computer. I currently have just the board and battery connected to a PC. I had a fastboot driver to come up for a split second, but I have no idea how or why. I am not sure if I bent the board just right, which allowed a contact to be made, but I have not been able to replicate it.
Does anyone have any ideas? The phone is screwed for sure, so if there is anything extreme I can do to save his pictures, I will do it. Thanks in advance.
First, I will say that I have done an extensive amount of searching and reading about boot loops and issues with the Note 4 before posting this. After days of dead ends, I have to ask for help...
About a week ago (end of January 2017), I installed the Verizon security patch update for Android 6.0.1 for my Note 4 (SM-N910V): MMB29M.N910VVRS2CQA1. Everything was normal until this past Friday night, when I used a flashlight app (had been installed since I had the phone and used often) and it spun into a bootloop. Battery was at 20% at the time, and since I've had the phone, the battery quickly discharges below ~15%.
Situational Details:
Anyways, the bootloop goes all the way to the home screen, and often the touchscreen is active for a few seconds (varies) before it freezes for 5 seconds and continues the bootloop. It's worth noting that during the bootloop, the screen gets incrediby hot at a specific point: horizontally across from the power button and vertically below the light sensor.
Also, I'm able to access the recovery menu, download menu, and boot menu. Also, when a power cable is connected to the phone (with battery inside), the phone screen shows the empty charging battery symbol and then immediately turns on, without me having to press the power button. After that, the only way to actually power off the phone is to remove the battery or let it bootloop until it dies.
So far, I've tried the following without success:
-Wiping partition cache
-Factory data reset
-Flashing stock ROM with Odin. Though Odin recognized the device in the USB port and it accepted the ROM which I loaded it with, there was no activity from Odin to the phone once I clicked "Start". I'm using the original USB cable that came with the phone (the one that I charge it with), and the USB port is working fine.
-Using Kies3/Kies2.6/Smartswitch to revert back to factory stock ROM. Though Kies3 is allegedly the correct software, they all display an error message that my device is not supported, when I attach a USB cable to my laptop from my phone (regardless of USB port).
-When using Kies3 to try Tools > Firmware upgrade and Initialisation, Kies accepts "SM-N910V" as the model number, but it displays an error message that my S/N is incorrect, though I am copying and verifiying the IMEI from under the battery compartment (I also registered my phone with Samsung using this IMEI, so I know it's valid).
-Wiping partition cache 5x + Factory data reset 5x before rebooting
When in the recovery mode, the current android version MMB29M.N910VVRS2CQA1 is listed, which I find incredibly bizarre, since I thought it would have flashed to the stock ROM after a factory data reset. *shrug*
It's crossed my mind that the exceedingly hot temps may be causing the boot loop, but genuinely do not know if that's true or why it would become so hot in the first place. Either way, I just want to toss the idea out that maybe I have a hardware issue that's causing such overheating.
Anyways, at this point, I'm totally confused about what to do, especially since it's not totally bricked. Any/all help is greatly appreciated.
Anybody have any thoughts at all? I'm more and more open to the theory that it's overheating and causing a boot loop. When it's been sitting for a long time at room temperature, the screen remains at full brightness on the Verizon splash screen, and does so until it gets stupidly hot near the microSD / SIM slots... then it boots up for ~5-15 seconds, freezes for 5 seconds, and boot loops again.
I may try to thoroughly wrap my phone in plastic wrap and apply an ice pack before attempting to use it again. I find it hard to believe that the culprit is batteries since the issue happens with both batteries that I have (purchased separately at different times).
Ok, I had my Note 4 totally cold yesterday and booted it up normally. I discovered a few things while playing with it:
When the first reboot happened,the usual hot spot was hardly to room temperature. I tried this exact same test again this morning, with the same results... the hot spot was not even to room temperature when it froze and rebooting.
It's worth noting that I figured out the screen does not freeze if the display is constantly moving, regardless of phone temperature. For example, I normally try to do something/anything prior to the phone freezing and rebooting, like establish a file transfer type usb connection to my laptop, instead of the default 'charge' type connection. Well, to go through the settings menu and pick out the connection type, the screen will always hang for a split second as it loads the next set of menus. Normally, it would freeze at this point and reset. But today, I decided to click on the Apps button and oscillate my finger on the screen to flip between pages of apps... and it worked for several minutes straight.
I know my problem seems incredibly strange, but do any of these symptoms have any plausible explanation? I'd hate to think there is literally nothing that I do and that my $$$ Note 4 phone is now a brick.
1weirdtrick said:
First, I will say that I have done an extensive amount of searching and reading about boot loops and issues with the Note 4 before posting this. After days of dead ends, I have to ask for help...
About a week ago (end of January 2017), I installed the Verizon security patch update for Android 6.0.1 for my Note 4 (SM-N910V): MMB29M.N910VVRS2CQA1. Everything was normal until this past Friday night, when I used a flashlight app (had been installed since I had the phone and used often) and it spun into a bootloop. Battery was at 20% at the time, and since I've had the phone, the battery quickly discharges below ~15%.
Situational Details:
Anyways, the bootloop goes all the way to the home screen, and often the touchscreen is active for a few seconds (varies) before it freezes for 5 seconds and continues the bootloop. It's worth noting that during the bootloop, the screen gets incrediby hot at a specific point: horizontally across from the power button and vertically below the light sensor.
Also, I'm able to access the recovery menu, download menu, and boot menu. Also, when a power cable is connected to the phone (with battery inside), the phone screen shows the empty charging battery symbol and then immediately turns on, without me having to press the power button. After that, the only way to actually power off the phone is to remove the battery or let it bootloop until it dies.
So far, I've tried the following without success:
-Wiping partition cache
-Factory data reset
-Flashing stock ROM with Odin. Though Odin recognized the device in the USB port and it accepted the ROM which I loaded it with, there was no activity from Odin to the phone once I clicked "Start". I'm using the original USB cable that came with the phone (the one that I charge it with), and the USB port is working fine.
-Using Kies3/Kies2.6/Smartswitch to revert back to factory stock ROM. Though Kies3 is allegedly the correct software, they all display an error message that my device is not supported, when I attach a USB cable to my laptop from my phone (regardless of USB port).
-When using Kies3 to try Tools > Firmware upgrade and Initialisation, Kies accepts "SM-N910V" as the model number, but it displays an error message that my S/N is incorrect, though I am copying and verifiying the IMEI from under the battery compartment (I also registered my phone with Samsung using this IMEI, so I know it's valid).
-Wiping partition cache 5x + Factory data reset 5x before rebooting
When in the recovery mode, the current android version MMB29M.N910VVRS2CQA1 is listed, which I find incredibly bizarre, since I thought it would have flashed to the stock ROM after a factory data reset. *shrug*
It's crossed my mind that the exceedingly hot temps may be causing the boot loop, but genuinely do not know if that's true or why it would become so hot in the first place. Either way, I just want to toss the idea out that maybe I have a hardware issue that's causing such overheating.
Anyways, at this point, I'm totally confused about what to do, especially since it's not totally bricked. Any/all help is greatly appreciated.
Click to expand...
Click to collapse
Do you have USB debugging turned on? Do you have all of the USB drivers for Samsung phones installed? Are you using the stock USB cable when you use Odin?
If you can't get Odin to flash your firmware(it has to be the same version you have or newer, it can't be older), then you may have a hardware issue that is a result of the excess heat you mentioned.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Do you have USB debugging turned on? Do you have all of the USB drivers for Samsung phones installed? Are you using the stock USB cable when you use Odin?
If you can't get Odin to flash your firmware(it has to be the same version you have or newer, it can't be older), then you may have a hardware issue that is a result of the excess heat you mentioned.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I didn't have USB debugging turned on before. I turned it on (under developer options... which I barely have time to access before it restarts), but now both my laptop and desktop won't recognize the device via any USB port. I do have the USB drivers for Samsung phones installed and have re-installed them a few times, to be safe. Also, I am only using the stock USB cable when doing any of these things.
1weirdtrick said:
I didn't have USB debugging turned on before. I turned it on (under developer options... which I barely have time to access before it restarts), but now both my laptop and desktop won't recognize the device via any USB port. I do have the USB drivers for Samsung phones installed and have re-installed them a few times, to be safe. Also, I am only using the stock USB cable when doing any of these things.
Click to expand...
Click to collapse
Does the device show in device manager? What is it labelled as in device manager?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Does the device show in device manager? What is it labelled as in device manager?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Assuming you mean the device manager in Windows, it's only showing as "Unknown USB Device (Device Descriptor Request Failed)".
Two new interesting notes:
When I enter Maintenance Boot Mode (Down Volume + Power to boot) and select USB Debug Mode, it now just performs a normal reboot. I can't recall for certain if this was any different in the past.
When I have the ability to access Developer options, I can definitely see that USB debugging is checked. Also, when I select 'USB configuration', 'charging' is pre-selected by default. When "MTP" (media transfer protocol) is selected, the developer mode menu still displays the value as 'charging', even though subsequently accessing the 'USB configuration' sub-menu shows that MTP is selected. Weird.
1weirdtrick said:
Assuming you mean the device manager in Windows, it's only showing as "Unknown USB Device (Device Descriptor Request Failed)".
Two new interesting notes:
When I enter Maintenance Boot Mode (Down Volume + Power to boot) and select USB Debug Mode, it now just performs a normal reboot. I can't recall for certain if this was any different in the past.
When I have the ability to access Developer options, I can definitely see that USB debugging is checked. Also, when I select 'USB configuration', 'charging' is pre-selected by default. When "MTP" (media transfer protocol) is selected, the developer mode menu still displays the value as 'charging', even though subsequently accessing the 'USB configuration' sub-menu shows that MTP is selected. Weird.
Click to expand...
Click to collapse
Have you tried booting to safe mode, if it boots to safe mode then it's a user app or a user app update that is causing your bootloop. In safe mode you can uninstall whatever app or app update caused it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Have you tried booting to safe mode, if it boots to safe mode then it's a user app or a user app update that is causing your bootloop. In safe mode you can uninstall whatever app or app update caused it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yeah, I thought about that, too. I've tried safe mode even after factory resets + cache wipes and it still boot loops. ("Safe mode" does indeed display in the bottom left of the display/GUI) Good thoughts, though.
1weirdtrick said:
Yeah, I thought about that, too. I've tried safe mode even after factory resets + cache wipes and it still boot loops. ("Safe mode" does indeed display in the bottom left of the display/GUI) Good thoughts, though.
Click to expand...
Click to collapse
Starting to sound like a hardware issue.
Sent from my SM-S903VL using Tapatalk
Today my phone felt down totally flat. The screen hits the floor directly.
It carries a protector above the screen, and apparently it is the only part that broke down
The screen seems to be in perfect status.
But the problem is screen is not working. None light is shown, and no reaction is performed.
If I touch the power button during 20s, the phone vibrates and it seems to be restarted.
When I connect the charger, the led works fine. Although no sound is played.
I would like to repair the phone, but at least (and this is important) I need to download all the data to the PC.
Question: is there any way to access to the data in the phone without having the screen available?
PHONE: MI9
OS: MIUI12.5
Yolco said:
Today my phone felt down totally flat. The screen hits the floor directly.
It carries a protector above the screen, and apparently it is the only part that broke down
The screen seems to be in perfect status.
But the problem is screen is not working. None light is shown, and no reaction is performed.
If I touch the power button during 20s, the phone vibrates and it seems to be restarted.
When I connect the charger, the led works fine. Although no sound is played.
I would like to repair the phone, but at least (and this is important) I need to download all the data to the PC.
Question: is there any way to access to the data in the phone without having the screen available?
PHONE: MI9
OS: MIUI12.5
Click to expand...
Click to collapse
If you did not USB debugging enabled in system settings before the screen broke, you will not be able retrieve your data. Now that your screen is broken, there is no way for you to enable USB debugging in order to retrieve your data.
Your options are:
1) repair the screen so you can retrieve your data.
2) forget about your data and get a new device.
Live and learn. I keep USB debugging enabled on all my devices for this very reason.
I found that I can retrieved my data thanks to custom recovery. I had a bit of lucky because with adb, data can be retrieved trhough custom recovery.
Usually, I have USB debugging activated but this time it was not activated as from last ROM update it is deactivated by default.
Now, I will deassembly the phone just to understand which is the root cause as touch sensor is working fine. So I need to understand if the problem comes from the screen or in the worst-case from connectors or PCB. In this last case I would need to get a new device, and I would like to keep this one for a few more time, even when there is no more OS update.
Yolco said:
I found that I can retrieved my data thanks to custom recovery. I had a bit of lucky because with adb, data can be retrieved trhough custom recovery.
Usually, I have USB debugging activated but this time it was not activated as from last ROM update it is deactivated by default.
Now, I will deassembly the phone just to understand which is the root cause as touch sensor is working fine. So I need to understand if the problem comes from the screen or in the worst-case from connectors or PCB. In this last case I would need to get a new device, and I would like to keep this one for a few more time, even when there is no more OS update.
Click to expand...
Click to collapse
I was going to suggest that but wasn't sure you would actually be able to install it or even if a custom recovery existed for your device since you didn't post what model you have. Also, if you had needed to unlock your bootloader to flash a custom recovery, unlocking the bootloader would have wiped your data.
Yes, you were lucky, most users in this condition are screwed out of recovering their data.