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!
Related
My Salutations, I am asking a question in regards to a serious bootloop I have managed to pull myself into.
Most bootloops I usually just enter CWM and flash another rom or restore. This problem however is much more serious.
Every time I attempt to enter CWM it goes directly to download mode. It's as if CWM doesn't exist on my phone anymore or something.
Download mode is the only thing I can access. I have tried multiple attempts to enter any other recovery mode but they all end up getting me to download mode.
This isn't the only problem. I thought this wouldn't be a big deal until I realized my PC can't recognize my phone at all anymore. Even before I got into the bootloop, my phone would only charge but any other recognition from the PC was absent. I have all the correct drivers installed including numerous attempts at re-installing, re-configuring, and restarting my PC.
I think I may have reached an irrecoverable error.
Any ideas would be much appreciated. Thanks.
FYI, The ROM I flashed when my Phone started acting like a bundle of ninnyhammerness was AOKP milestone 6. It's not the ROMs fault of course, seeing as how this ROM is very good. I also had the Darkside kernel. This is when I couldn't manually enter CWM. In stead, I had to let the phone boot up and utilizing the power menu, restart in recovery mode. I thought this was strange at first. I then wiped, and decided to flash the 20th Nightly of AOKP Jellybean just to try it. It booted fine, but then when I had to restart to enter CWM again I chose to flash another Darkside kernel. After this, my phone went into a bootloop. That is where everything else fell apart.
Sounds like either the recovery isn't sitting in the system correctly or its gone. When your phone is in download mode you said that you can't connect to pc. Are you running odin as admin and/or connecting the device to pc previous to putting the battery back?
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Yes I did run Odin as an administrator. I also tried connecting the device prior to putting the battery in, and also after.
I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!
kmcclry said:
I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!
Click to expand...
Click to collapse
Thanks but, it still hasn't worked. It keep saying "USB device not recognized, Device driver software was not successfully installed."
I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.
i3lackDawn said:
I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.
Click to expand...
Click to collapse
also it may be because of a faulty data cable !
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
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.
Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
daiichi said:
Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
Click to expand...
Click to collapse
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
treacherous_hawk said:
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
Click to expand...
Click to collapse
Thank you for your help Sir.
But, my Find 7 already operated normally again since I left it for a few days uncharged and off.
Then I got into Recovery Mode by pressing Power button and Volume Down button (not Volume Up button) while in the middle of my fast-boot loop.
It worked. I could gain access to ColorOS Recovery Mode.
So, I reset my Find 7, then re-installed my applications and everything again.
Thank you for answering!
The phone when trying to boot is stuck on the samsung logo. it doesnt progress past this. pressing and holding the power button makes screen go black and then it just returns to the samsung logo again when power button released.
Originally factory
reset phone... no difference,
wiped cache... no difference.
Got it to register in Odin. Odin crashed and hung part way through.
Now... computer doesn't recognise phone (drivers all installed)
Phone still stuck on samsung logo
Can't put in a file on SD card as it doesn't have option to install from zip from SD (think it was standard ROM and not rooted so doesn't have this ability from what I understand.)
Can get into recovery menus and download mode, however as PC can't recognize the phone can't do anything with it.
Anyone have any idea how I can make the computer recognize the phone so I can attempt to reflash it?
Many thanks
I have just gotten a new cable. The phone has been accepted by my computer with this new cable and I've now used the files on this forum to help flash the phone. This site is fantastic. I know noone has mentioned a response to this yet, however the ROM files accessible make it so easy from here. Thanks so much.