Ive got a note 8 that just died on me today. The screen remains blank no matter what I do. When I plug into any charger, it sends out random short vibrations usually every few seconds. Ive tried rebooting, force rebooting, recovery booting, nothing lights up the screen. No combination of volume and power keys accomplish anything. The battery had around 40% when it went out. Please help me recover this thing! Ive replaced the battery and LCD on it once. I really don't want to just throw random parts at it hoping for a fix. Yes Ive checked every connection to be secure. I am thoroughly stumped.
Skytex said:
Ive got a note 8 that just died on me today. The screen remains blank no matter what I do. When I plug into any charger, it sends out random short vibrations usually every few seconds. Ive tried rebooting, force rebooting, recovery booting, nothing lights up the screen. No combination of volume and power keys accomplish anything. The battery had around 40% when it went out. Please help me recover this thing! Ive replaced the battery and LCD on it once. I really don't want to just throw random parts at it hoping for a fix. Yes Ive checked every connection to be secure. I am thoroughly stumped.
Click to expand...
Click to collapse
Connect the phone to the PC and then open a command prompt window where you installed ADB and run adb in the command prompt window and when it opens then type adb shell reboot recovery and see if it reboots to recovery mode but it requires that you have USB debugging enabled in developer options and if it's not enabled then there's nothing else you can do.
Its totally stock. Never installed adb on this phone
Skytex said:
Its totally stock. Never installed adb on this phone
Click to expand...
Click to collapse
Adb is "installed" on your computer, not phone. Adb/fastboot commands are delivered to the device.
https://developer.android.com/studio/releases/platform-tools
Related
So I've run into quite an annoying problem- I can't install applications from the market. Last night, I had my phone plugged into my computer and I don't THINK I had the SD mounted, but I've been wrong before. Anyways, I went to disconnect it and instead of dismounting then unplugging, I just unplugged. Since then, if I try to download something, the notification bar will show that the app is downloading, for a second, then it just disappears. My phone is rooted, no custom rom though, and I'm not running Apps2SD. Also, I'm running Ubuntu 10.10 x64 on my computer.
This has happened once before, and I had to tinker with popping my SD card out and rebooting the phone a few different ways before it finally started acting right again. I'm looking for help because 1) I can't remember exactly how I did it and 2) I figured I might as well try to find out if anyone here knows what I could do to fix it.
Thanks in advance.
Galaxy S Showcase stuck at very first screens
Afternoon guys, I did some browsing and searching and cannot seem to find a way to fix this, so here goes:
Samsung Galaxy S i500, Showcase with Cellular South.
It is rooted, with the original ROM/Kernel.
Yesterday, I was attempting to follow the guide on getting ClockWorkMod on it (http://forum.xda-developers.com/showthread.php?t=860250) and when I finally got the final command to work, the phone rebooted, and has since been doing VERY little.
Power Button = SAMSUNG... No vibrate, No change.
Vol Up/Down + Power = SAMSUNG... No vibrate, word flashes, release power (steps to enter recovery or download), SAMSUNG screen remains. Still no vibrate or anything.
Plug in = Grey battery with "loading" circle with no animation of any kind. It is charging though.
Plug in + Vol for recovery/download mode = still just grey Battery not moving.
In all attempts, I have left it trying for anywhere between 30 mins to 4 hours... I cannot get to anything but those 3 results. (samsung, samsung w/ 1 flash, and grey battery).
If I can get it into Download, I can Odin it, or recovery to reset to factory... but I need to get to one. Any and all help is appreciated.
~*~*~Artilleur~*~*~
Download Mode
I had similar situation. Could not get past samsung screen. No splash screen.
Download mode. Pull battery, Plug in USB, hold Vol-. Little guy with shovel.
As for getting back to running. Good luck. I got new warrantied phone couldn't figure out how to fix after soft brick.
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
horgenblorg said:
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
Click to expand...
Click to collapse
The symptoms you describe suggest a hardware vs software problem. Guessing bad memory (or controller) given the random boot behavior. Unfortunately, there is little you can do to rectify the problem, even if software based, on an unrooted 4th gen HDX. ADB will not allow privileged access unless the device rooted.
Look on eBay for another motherboard. Might also want to grab a daughterboard as well.
Watch some teardown videos on YouTube. Everything applies to the 4th gen as it does from the 3rd gen as far as taking it apart.
In total you can fix it for around $65. That's with buying both boards which you possibly only need the motherboard.
Sent from my KFSAWI using Tapatalk
Hello everyone,
I've been a reader for a while, purely out of interest. I've never really dabbled with customizing android. In that regard I am a noob... I recently acquired a Medion X6001 that I was planning to build into my car as informant/navigation. Phone root successful, developer options active, debugging and oem options active. Automate programmed to all the standards I was happy with., worked great. All that was left to do to was get the thing to boot on charge. The "fastboot oem off-mode-charge 0" command was unsuccessful so I resorted to trying to find the system file responsible for battery icon on charge with power off.
That's where I went wrong. This phone has two icons; first a battery with a bolt, then switches to another with blue fluid and battery percentage. I found the blue fluid battery icon - 'system/bin/kpoc_charger', unfortunately I needed the killswitch battery icon. So I made another guess and renamed - 'system/bin/lmkd'. This was the file directly before ...kpoc and my daft logic lead me to believe that that might have been the right file. Obviously, it wasn't.
So the problem? The phone won't boot. Not really... At first, it was entirely stuck in bootloop. So, the good sheep I am, I factory reset the phone through recovery. The phone still went into bootloop for a few minutes, but came out of it to an applet saying 'optimizing apps'. Took 10 minutes to optimize and then went through to another applet saying something along the lines of "system process not found, do you want to wait?". Behind this applet I could tantalizingly see the startup screen of a freshly reset android.... It gave the option to wait or push ok, neither of which were actually active to touch. If I held the power button it would give me the option to shutdown, reboot or screenshot, also none of which where actually active to touch.
So after more googling, I wiped the cache through recovery. Everything stayed the same; bootloops for a few minutes then applets. Only now everything is in Chinese kanji... which is why I can't reiterate verbatim what the applets originally said...
After around 12 hours of tirelessly searching the web I've tried everything I've found but every time I get through a door there's another one closed. I can't install twrp or clockwork, I can't flash the rom, the phone won't let me unlock the bootloader in fastboot. Went I type the command it asks if I want to unlock it: volume up yes, volume down no. But fails: "remote access denied"
Since the factory reset, I don't have access through adb anymore. If I let the phone boot I can see it connect to the computer, but only as mtp. The file is entirely empty. I have no access to usb debugging. And to remotely access that, I need to be able to unlock the bootloader.
I can't get around the blocks and everything that is advised to get around bootloops and flash through fastboot are seemingly impossible because I no longer have proper access. But I can't get into the phone to get access...
And to make matters worse, just now as I type this.... I can't get into fastboot anymore. I think the phone battery is dead, but apparently doesn't accept a charge. When I plug it in the battery symbol appears, the dark red led lights up indicating very low battery. Very shortly after that the led turns off, which is not how it was before I buggered everything. Battery icon stays on, but when I push the necessary buttons to get into recovery, everything goes blank and the phone does nothing. When released, battery icon comes back and red led for a few seconds. Repeat. Phone has been plugged in all night....
I'm nearly bald from pulling my hair out. I hope there's someone out there that can give me a hand. I have a hard time believing I bricked the phone just by changing a bin file name.
Thanks in advance!
fastboot
I have access to fastboot again. Plugged the phone into a different cable, is now charging. I can see the battery % through recovery.
Back in business....sort of.
Any idea's welcome.
bump
Anyone?
Well I found the ultimate cure: buy a new one.
I will however keep fumbling around with the other one and hopefully as my knowledge increases I'll have a break through.
I was searching for a solution for my contact sync issue and I needed to reboot. After pressing reboot, the screen goes blank and I cannot boot again. Volume up + power doesn't work. Plug in power and the light didn't turn on. Even try to hit the tiny hole that looks like reset and that didn't work with. Help!
I am on official miui 9 with Google installer
Did you hold the power button for a longer time?
Yes, try holding the power button for some time. One time, after fastboot, it took around 90 seconds to power up.
there's a tiny hole that looks like a reset ????
did you poke the mic hole?
rioru said:
Yes, try holding the power button for some time. One time, after fastboot, it took around 90 seconds to power up.
Click to expand...
Click to collapse
Hi Rioru, did you ever find a solution to your issue. After charging last night, suddenly I had exactly the same error. Which means I cannot boot the tablet, Power+Volume UP does not respond, charging LED not responding and after connecting to a PC I cannot not establish an ADB connection.
Thanks!
mailis said:
Hi Rioru, did you ever find a solution to your issue. After charging last night, suddenly I had exactly the same error. Which means I cannot boot the tablet, Power+Volume UP does not respond, charging LED not responding and after connecting to a PC I cannot not establish an ADB connection.
Thanks!
Click to expand...
Click to collapse
Hi, I think you're quoting the wrong person here. It's not me, it's spx2000 had this problem.
I have two...1st mi pad 4 flashed many ROMs looking....2nd mi pad 4 on first flash device will no longer boot. PC with miflash starts flash but errors on com port. I have tried cables and different ports. Need help . Black screen
Tablet is seen in win as Qualcomm....miflash sees device as I try different USB ....flash always errors unable to read comm port xxx. Not sure what to try next.
Same issue here, MiPad4LTE. Mine just died while playing mobile legends. Power wont turn on. Even when charger is plugged, LED won't light.
I bought a used Zenwatch 2 and after a week it stopped working. When I turn it on it sticks on the Asus splash screen. After talking to customer support and looking online it appears that the "firmware has been corrupted.
I made the mistake of not turning on ADB Debugging while it worked, and unfortunately the screen appears to be unresponsive so I can't even put it into Fastboot mode to turn ADB Debugging on. Of course to make it even better the watch is not recognized when I plug it in because it doesn't appear to boot enough. Since I can't get into anything it makes it impossible to reinstall the firmware.
You all are my last hope, does anyone have any insights into a way to get the phone recognized, or anything that may help? Please help me keep this from becoming a fancy bracelet.
When you first turn it on, swipe diagonally down from either direction to get into recovery or fastboot. I know you said the screen is unresponsive, but if you haven't done it before it can be tricky. Even on a perfectly working watch, I still have trouble getting it to work. Try continuously swiping as you hold the power button, even before the splash screen shows up. If you can get it into fastboot, unlock the bootloader and try flashing my ROM.
CVertigo1 said:
When you first turn it on, swipe diagonally down from either direction to get into recovery or fastboot. I know you said the screen is unresponsive, but if you haven't done it before it can be tricky. Even on a perfectly working watch, I still have trouble getting it to work. Try continuously swiping as you hold the power button, even before the splash screen shows up. If you can get it into fastboot, unlock the bootloader and try flashing my ROM.
Click to expand...
Click to collapse
That seems to be what I am reading, but so far I have had no luck getting it to trigger into fastboot mode. I will keep trying.