really need some help....
so i managed to get p.a flashed and running on my galaxy nexus, though i noticed it was a bit laggy on system ui.
surfaceflinger looked to be the fix to my issues, though maybe i installed the wrong version, idk.
turning on the device, gets it to the google logo, where it just hangs, and only way to turn it off is with a battery pull.
i can get into bootloader just fine, and recovery
i have no back ups to restore from, but no data to lose.
when plugged into a computer in bootloader, computer acknowledges device, but as an "unknown device" in the USB controllers section on device manager.
when plugged in in system mode, the computer acknowledges something was plugged in, but nothing in device manager.
i'm a bit of a noob at all this, and just looking for the easiest solution to get me back on track, any help would be greatly appreciated
Reinstall
try reinstall the rom..perhaps your are skipping some steps..wipe all the neccesary things
Related
Update: The 100th or so time I tried to boot into recovery, miraculously it worked!!! I have no idea why. I reflashed and did a soft wipe, and now all is good. The phone's internal memory only had about 225 MB of storage space left, so maybe that caused the problem, or maybe not. Thanks to everyone who tried to think of possible fixes.
Hi, I did a really stupid thing last night. I backed up with TB and uninstalled my gallery app to try another one that I didn't like. (I have QuickPic installed, as well as third-party camera apps.) So I uninstalled that one and then tried to restore the original gallery app again with TB. For some reason the install hung. What I should have done was force-close TB and install the APK again directly, but instead I rebooted the phone. Or tried to. As it turned out, I hard-bricked it.
The battery icon displays. When I try to turn on the power, the Samsung logo displays and then the phone turns off again. I can't boot into recovery or download mode at all. When I connect to my PC via USB, I get a boot-looping pop-up on the PC taskbar: "Found New Hardware/SAMSUNG Mobile MTP Device." The device screen stays black. ADB won't start. I reinstalled the Samsung drivers just in case, but no love. The Windows device manager doesn't show any problem with the drivers. Odin does recognize the device up to a point: a yellow box lights up and there's an "added" message, but nothing more. At this point, all I can think of to do is get hold of a jig as soon as I can and pray that I can get into download mode and connect to Odin. I am (or was...) rooted and running CM 10.2 stable.
How likely is it that the jig will work? And does anyone have any other suggestions? I'd really appreciate them. I don't have a landline, and it's a bummer not to be able to make calls so close to Christmas.
Thanks a lot for your help. I really appreciate it!
Trying to flash the stock ROM here, but ODIN isn't working. ID:COM doesn't turn blue! I've booted my Note 8 into download mode, but absolutely NOTHING indicates that anything has been connected. The regular Android has been disconnected, and NOTHING new gets connected that might be the "download mode" device (whatever that device may be).
How do I get this to work?
For reference, at the ltop left of the screen, it says:
ODIN MODE
PRODUCT NAME: GT-N5110
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
NOTHING CHANGES IN THE DEVICE MANAGER WHEN PLUGGING IN THE DEVICE
This leads me to suspect I need to do something on the device itself to get it to "do" something, whatever the flipping heck is needed to make a pc connection.
Kies has been installed. Same problems before installing it.
I've used the Toolkit from skipsoft, and used the drivers that came with it. No change before or after.
I've installed and uninstalled and reinstalled drivers, and more dirvers, but nothing.
NONE OF THIS WORKS.
USB connection for ADB mode works fine, both in recovery and when fully booted.
Android is currently Cyanogen 11, pc is Windows 7. I'm trying to get the stock ROM on it again, I've got it ready for upload, now all that remains (hopefully) is to get the device to connect so that it can download the "update".
Please help, I'm out of ideas.
Okay, time for an update. For some odd reason, the tablet needed to be plugged into a USB 3.0 port in order for download mode to work. Very odd. Very odd indeed. NONE of the guides mention anything about this, but apparantly it's a thing.
Anyway, Now that I'm back to an official stock ROM with Android 4.2.2, booting the device takes abnormally long. It's been in a boot process for the last 10 minutes now. IT DOES NOT LOOP, it just shows the samsung logo with an animating blue glow behind it. And nothing else.
The tablet is quite warm, which is nice for my hands, but not great for the battery. It will probably drain out in the next hour.
When I connect the tablet to the pc (on the USB2 port again), it detects a normal range of Android devices. They all install normally, except for the MTP device - that one fails. Not sure if related, but it's a thing that happens nonetheless.
What can I do to make it go and boot through to Android?
Boot into stock recovery and factory reset... wipe cache... should take care of the excessive boot time.
Today hasn't been one of the better ones this week. Putting aside my pride for a moment, here's what happened. In my frustration, I threw my phone into a cardboard box. Aiming for the side of the box...it ricocheted of the floor then the side. Yeah, not the best available option to vent!
So...screen spiderwebed and the screen will no longer turn on. Phone vibrates when the power button is used, yet screen is blank.
I'd like to ask for help for the following:
Retrieve several important files that weren't back yesterday: Pictures & program files not synced for privacy reasons, plus TWRP backup from a couple of days ago to internal memory b/c SD full.
Screen damage or more involved? To determine if I spend time fixing or buying a replacement phone.
Phone is the Canadian Koodo T989D running CM11 8/04 with TWRP 2.7.1
Phone Symptoms:
After removing and replacing battery
Pushing power button - Normal 'turning on' short vibrate, screen doesn't turn on (no light/pixels light up)
Recovery Mode - Normal Vibrate, release pwr button and again screen blank with exception of top Left corner showing multiple pixels, unrecognizable
Download Mode - Plugging in the USB cord causes the phone to vibrate every 2 or three seconds and the cycle repeats. vibrate...vibrate...vibrate...continuous
Any thoughts on troubleshooting to determine if retrieving files on the phone is still an option?
Would appreciate ya'll sharing your common knowledge that uncommon while I'm this frustrated. After switching to an AWS service provider (WIND) 2 weeks ago my backup phone isn't compatible - Galaxy Ace GT-S5830D. Thought it was until I tried, then realized it isn't. I'm kind of flustered that I acted so impulsively and doubly because I thought I had a backup phone, ughh!
I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?
MASTERBLASTER69 said:
I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?
Click to expand...
Click to collapse
Thanks for the educated guess and ADB suggestion to recover files.
Yes the computer shows 3 drives when attached in Recovery Mode. And darn it I can't remember if debugging on or off. The computer doesn't recognize the phone by default while in recovery mode. If this is the case, would ADB likely allow access to the phone? Not a tool familar with yet.
Unlikely that the battery is damaged if the phone turns on. Still stays cool while on or charging. Which is good news.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.
the computer shows 3 drives when attached in Recovery Mode.
Click to expand...
Click to collapse
I don't understand why you see 3 drives... I'm sure Windows will ask you to insert removable storage if you try to access the drives, right? If that is the case, and you have no screen/touchscreen, only ADB will allow you full access to everything in the phone.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.
Click to expand...
Click to collapse
Yes. Here's the tricky part though, in order to make adb work, your computer needs the right drivers for your phone.
I think you should try to follow the HOWTOS (How to Install Android ADB Interface Drivers) on installing the drivers for ADB.
If all goes well, you can check if it worked by typing 'adb devices' from the windows commandline. Then it would be possible to use adb to get your files back.
If the phone boots into the system...if, since you can't see it....you should be able to open the sd folder on your pc and simply copy/move what you want to the pc.
Just checking if you've tried this.
Ok, So I am extremely stupid. I installed TWRP, and I clicked on the botton which says "Delete /System", So after that, It seems that when booting up, It displays the Kindle Logo, and that is it. Literally. And when I tries to unbrick it, none of the tools recognize it. I tried FastBoot cables, no luck. And one time, I'm not sure how I did it, but I managed to make the tool(Forgot its name) to recognize it, but it never able to push back the new bootloader and system file back... Anyone can fix this for me? I'm willing to pay $10-20 for anybody that came up with a solution that works. Thanks.
Update failed
Eric1084 said:
Ok, So I am extremely stupid. I installed TWRP, and I clicked on the botton which says "Delete /System", So after that, It seems that when booting up, It displays the Kindle Logo, and that is it. Literally. And when I tries to unbrick it, none of the tools recognize it. I tried FastBoot cables, no luck. And one time, I'm not sure how I did it, but I managed to make the tool(Forgot its name) to recognize it, but it never able to push back the new bootloader and system file back... Anyone can fix this for me? I'm willing to pay $10-20 for anybody that came up with a solution that works. Thanks.
Click to expand...
Click to collapse
I am sorry if this is not an appropriate response, but the thread looks similar to my problem. The user does not wish to ROOT the unit, only get it functioning! My son attempted to update his Fire2. Now it seems to have a Launcher problem. The unit boots to the swipe screen, but swiping gets the following:
"The application Launcher (process com.android.launcher) has stopped unexpectedly. Please try again. <force close>"
I can't find any way to get past this. I can view the files from my PC via USB. Can I install a new launcher from this link?
Factory Cable
oldtex said:
I am sorry if this is not an appropriate response, but the thread looks similar to my problem. The user does not wish to ROOT the unit, only get it functioning! My son attempted to update his Fire2. Now it seems to have a Launcher problem. The unit boots to the swipe screen, but swiping gets the following:
"The application Launcher (process com.android.launcher) has stopped unexpectedly. Please try again. <force close>"
I can't find any way to get past this. I can view the files from my PC via USB. Can I install a new launcher from this link?
Click to expand...
Click to collapse
A new response. From other posts, I made a "factory usb cable." The Swipe Screen changed, but the unit response did not. Still can't get past the Launcher problem. Anyone have a plan for getting past this issue?
I'm in the same predicament. My son was trying to re-flash a rom I had placed on the KF for him (after having a Google sign in error problem) and during wipe, he hit "system" not realizing it would wipe the entire thing. Now it's booting into the logo screen with orange "fire", then into the blue "fire" logo screen and staying there. He is having a FIT and I cannot seem to find a solution to the problem that does not require a fast boot cable (since it says it will be 2 weeks before it gets here). It's not a full hard brick since it still boots, but I get no option to boot into the recovery, since I am assuming that too is gone from the Kindle. I guess I just assumed it would be as easy to fix and my Android phone. Is there no option to return it to stock with the included USB?
So, the other day my phone started acting weird. It randomly restarted, then worked another hour or so, and then started shutting down almost immediately after booting. I was running a Nexus 5X with rooted stock Android 7.0.0 (SuperSU root) and ElementalX kernel. It had been running this for a few months without any issues. I can't think of anything I did to trigger this. I didn't run any updates, I haven't flashed anything since I installed ElementalX couple months ago.
After a lot of troubleshooting (at first I could still get into the bootloader and recovery, but when I did, TWRP didn't recognize any partitions? I was unable to access the file system in TWRP), it finally got so bad that my phone is no longer recognized by my laptop other than "QHSUSB_BULK" device in the Device Manager (Windows 10 x64). Completely black screen, no response, no LED when plugging in adapter. One time I managed to get into the bootloader (randomly, no idea what triggered it) and I managed to put stock 7.1.1 on it, but soon after the installation of that, the exact same thing happened: random reboots, progressively getting worse to in the end: no recovery, no bootloader, only recognized as "QHSUSB_BULK". So I was back to the lowest point.
I read about a "hidden second bootloader" on the 5X, that would be accessable through Power+Both Volume keys, but that doesn't work at all for me (tried it for up to 1 minute of pressing).
After hours of searching (I probably read all the 5X + other phones's topics here that have this issue..), I came here: www.droidsavvy.com/unbrick-qualcomm-mobiles/
I followed those steps precisely, got my laptop to recognize the phone as 'Qualcomm HS-USB QDLoader 9008' by installing the Qualcomm drivers with driver signature verification turned off, but I just couldn't get the QFIL program to flash anything to my phone. It threw a "Download Fail:Sahara FailSahara Fail" saying it couldn't send the Flashing program to my phone. I tried several things here: attempted to power off the phone, then hold Volume up+plug in USB --> flash straight away, different driver/software versions, different laptop, but all to no avail.
I have no real way of telling whether the phone is on or off (it seems impossible to actually turn it off - if I hold power for 30 or so secs I do hear the USB disconnect-connect sound from my laptop, but the device is still shown as "QHSUSB_BULK" so it won't actually turn off properly).
My current hypothesis: it's a hardware fault (eMMC?) and as I'm still within warranty I can send it in for repair/replacement.
Perhaps there is a very slight chance that someone has also encountered this, and it's still a software problem which can be helped by me in some way?
Thanks in advance!
Its probably some part of the motherboard that is faulty. Take it into a repair center. Get it replaced.