Hi guys,
first of all thank you for taking your time and reading through this. I'm not completely new to android, nor using fastboot and recovery. I flashed a few phones over the past years I even resurrected bricked ones. However I have no idea what is happening to my Honor 8. One thing to mention, it's the latest Nougat update, and a STOCK ROM.
It all started this afternoon. The phone suddenly reboot while using it. After that, the android screen came on, then Honor animation and.. freeze. Completely. I had to reboot using the long press method since it was stuck between the bootloader and the rom itself. It started up ok after that.
An hour passed, and while I was typing a message, it froze again. I could go back to home but the phone was really slow. After opening up Messenger again, it froze completely. Had to restart again with the long-press reboot method. It started up ok, entered the sim pin and upon entering the screenlock code it froze again, completely. Long-press reboot, again.
Since then, the phone won't boot. It gets stuck every time on "Honor powered by Android" for about a minute, then it reboots itself. I even got some weird green screen with a blue and a red rectangle, but that just stopped after a few reboots.
I mentioned that I know how to recover and fix stuff when something acts weirdly, but that's not the case, I can't do ANYTHING. No fastboot, no recovery, no button combinations, I can't even turn off the phone. It just keeps rebooting on and on, and yes, the battery will eventually die, but I have no access to any recovery options. I even tried dload but no luck.
It's still under warranty so I can send it back but I just rather fix it at home (without taking it apart), because I don't want to wait 3 weeks to get fixed. But it seems like that is the only option right now, I have never ever seen anything like this happen.
Any help or comment is appreciated. Even if it's not possible to do it at home (hardware issues?), I am really curious what can be the cause of this issue (damaged rom, filesystem permission issues?).
Thanks.
Related
Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.
Hello all,
I am merely posting here if anyone has a better insight or idea, since I haven't followed with all issues regarding the Galaxy S II International version.
I have purchased mine from one of my country's carrier nearly 2 years ago. I have in the course of these 2 years, rooted it, flashed CyanogenMod, and happily updated it every so often. I always used nightlies, updating almost everyday.
In the last 2 months, it had become sometimes very sluggish, frequent slowdowns, and many lockups, freezing, and some random reboots. I was getting a little tired of it, but was getting used to it.
Yesterday, I was using it normally, when a slowdown started. The app (was 3D game) got unresponsive, but I could still pull the notification drawer, so it wasn't frozen. I pulled and pushed the drawer about 2 times, and then it also stopped responding. The screen was on, touchlights were on, and since I had seen it before, I pressed the power button for a reset.
Then the first boot screen, with the yellow triangle (where it says Samsung Galaxy S II GT-I9100) appeared, but it got stuck there and didn't get past, apparently frozen.
I tried a quick more reboots, and then tried (with very difficulty) entering CWM recovery. I got eventually there, and CWM was working as it should. I considered wiping the cache, or just reinstalling the last nightly I had saved, but decided first to just press "reboot system now".
It also got stuck on the yellow triangle initial screen. This time I couldn't get to the CWM recovery (it seems there was a very small time frame to it to enter before it actually restarted again from long pressing the power button). In a dark room, I noticed that even when the yellow triangle screen was black, the display was on, the backlight was on. The black was bright, and if I pressed the powerbutton for a reset, I could see the screen actually turning off and then on again, and going back to the yellow triangle screen.
I tried to go into Odin recovery, and eventually made it there.... So I pressed to restart the phone, and it continued frozen on the yellow triangle.
I went home with the screen frozen (I couldn't power it off, and I didn't remove the battery). I noticed that after some minutes it restarted, the screen went black and again to the frozen yellow triangle.
I managed to get to CWM recovery after several attempts with the 3 button press, but a different error had appeared: E: Can't mount /cache/recovery/command (or something like it)
So I got home, downloaded codeworkx CWM recovery, put the S2 in Odin recovery, and using Heimdall uploaded it. It completed successfully.
I managed after several tries to get to CWM recovery, it opened again, but more "Can't mount messages" appeared, system_log and such, as I have seen on some forums, and that by then I never had. Read somewhere that probably the system partition got corrupted.
Then this time I reinstalled from the internal memory another nightly I had. I was with June 19, and used the June 16 one. It flashed successfully.
Then I pressed reboot system now, but still got stuck at the yellow triangle screen. And again the message "Can't mount /cache/recovery/command".
So I got into Odin recovery mode (volume down) and using Heimdall again uploaded CWM recovery. But Heimdall got stuck at "Loading KERNEL 100%" It reached 100% but never exited. And the bluebar that was supposed to appear on the S2 screen (that appeared the first time I flashed CWM), didn't appear.
Since it got stuck there for a while, I Ctrl-C'ed my way out of Heimdall, and pressed the power putton on the S2 for another reset.
But this time, it never woke up again. No more yellow triangle screen. No more "active bright black screen". Nothing.
And it doesn't charge even when plugged to the charger.
I am reading about SGS2 that won't turn on and won't charge. It seems a general agreement that Samsung assistance tells us it's a motherboard failure, and should be replaced (and at least here in my place it's helluva expensive).
Since many cases the phone just went dead, mine wasn't quite the case, since it was somewhat alive in the yellow triangle and apparently I could have f*cked up when I Ctrl+C'ed Heimdall and turned off the phone when Odin recovery clearly states "Do not turn off target !!", even though when the flash goes ok, you have to reset it.
Two questions:
1. Is there anything else that can I do to revive it?
2. Can I recover at least the pictures and videos I had saved on the internal memory? I had a ton of pictures and videos inside DCIM/Camera, where for a long time CM10.1 camera could only save pictures to the Internal memory, and when a nightly fixed it, I kept it in internal memory.
If anyone got this far since I was exhaustingly detailed, thank you for your attention!
Unpluging was the bad move that killed your phone. Can try a jig
andrewwright said:
Unpluging was the bad move that killed your phone. Can try I jig
Click to expand...
Click to collapse
Well I had just done the same process, and it was quick. There was no waiting period after the 100%, and Heimdall exited cleanly.
The last time it got stuck in 100% for about 30 seconds, and I decided to abort with a Ctrl+C, unplugged and restart...
My phone restarted one day and just wouldn't boot up. At first it was just stuck on the SAMSUNG logo, but after trying to boot into recovery, it now sits at the boot animation. When I try to boot into recovery, the CWM screen will come up, but no menu will show up, and then the phone will restart after a few minutes and go back to being stuck on the boot animation.
I can enter Download Mode, but USB Debugging must be disabled since ADB won't recognize the device and I can't send any commands (yes, drivers are installed).
First of all, is there any way I can recover the data on the phone? That is more important than getting the phone working, since I was just about ready to get a new phone anyway.
What can I do to get the phone working? Everything involving flashing a new kernel, or resetting the phone back to factory seem to require a working recovery or the ability to send commands through ADB, but I'm probably missing something, since there must something else that I can do.
Any help is greatly appreciated. Thanks.
**Not sure if this is related or not, but the reason why the phone restarted before this issue occurred is because the power button on the phone is a bit faulty. Over the past couple months I've been having issues with the power button; it seems overly sensitive so when I push it sometimes the screen will turn on and off and other times the phone will just restart as if I held the button down for too long. This is the main reason why I was ready to get a new phone.
Greetings,
My device is probably about three years old, I was totally satisfied until I noticed sudden change in my phone's performance about three months ago, way too laggy even after doing factory resets and etc.. , battery was being sucked faster than it supposed (even with a new battery), heating up whenever it decides to, not being able to handle hardcore-use which it could handle in the past... etc.
So, I took all that as a sign that my phone needs to be replaced. Last night while I was on my pc and the phone was sitting in front of me, I caught the phone restarting by it's own. I noticed this happening frequently over the past few months, and usually nothing wrong happens, although I had to remove the SD card once.
But this time its a whole different issue, the phone was stuck on "Samsung galaxy s III .. blah blah" , pressing the power button wouldn't turn off the phone and it would turn itself on the moment I put back the battery. I surfed the web for info and found topics that called this "stuck power button issue" and they suggested to smack the power button with battery or smack the phone itself (without holding any grudge against the phone ). I did that and it fixed the issue of the phone turning itself on.
At this point I found out the next issue, the OS won't boot & i would still be stuck at "Samsung galaxy s III ..." screen. So I tried to boot into CWM (Power+Home+Vol Up) but it would loop me back to the same screen 'till death >_>
Then I checked if I could enter download mode and it was a success, afterwards I downloaded a stock .md5 for my phone (and specified country), Loaded it to odin and tried to flash using that, and it failed on me ... check the pic below if you wanna see the error massages
(add http)
postimg.org/image/dz0c0mu8l/
FAIL !! I tried it twice, I can't think of what to do anymore ... Being able to access BBM (I got a habit of making notes there) & Contacts (I am not sure if superbackup was being a good boy and made backups everyday) would be nice .. But I don't think it's gonna happen ... All I really care about is being able to recover everything from my Internal storage, I don't care if the phone becomes unusable or whatever.. I just need the internal storage.
+ My phone is rooted, I have some nandroid backups and the Rom I was using was Android Revolution HD
Update 12/10
I messed around with the phone, and found out that I can still get in cwm, but I keep getting stuck with "can't mount cache/recovery/..." "can't open cache/recovery/..."error
Since the phone is three years old the battery could be the culprit. Try with your friends battery to see if the phone is booting properly. Still if your phone stucks in boot loop then repalce your power button.
I faced similar issue. My phone went into bootloop even when in recovery. It would reboot while OS installation is in progress. Weird. Rebooting while in recovery could damage the recovery itself and next time it wont even boot into recovery.
mpadhu said:
Since the phone is three years old the battery could be the culprit. Try with your friends battery to see if the phone is booting properly. Still if your phone stucks in boot loop then repalce your power button.
I faced similar issue. My phone went into bootloop even when in recovery. It would reboot while OS installation is in progress. Weird. Rebooting while in recovery could damage the recovery itself and next time it wont even boot into recovery.
Click to expand...
Click to collapse
thank god someone replied, I thought nobody would respond so I gave up on xda .. anyways I just updated my post.
I am positive that the issue is not the battery, since it's new and i did try the older one and nothing changed. I still get stuck at the same screen x_X
Hi all,
To get right to the point, my phone doesn't switch on, and I cannot get into recovery/download mode.
The story:
After my apps kept on crashing for no reason, I restarted the phone. After the restart, when it asked my pin, the google app kept on crashing and the phone completely froze up.
Here is where I suspect I made a HUGE mistake. I Took out the battery and started up the phone again. It immediately told me that the system is corrupt and "cannot be trusted".
I continue the boot process, only to land in a boot loop. I take out the battery once again and restart the phone.
After displaying the LG logo, it just turned off. And that was the last time I could get it on.
I tried booting into recovery, but the phone won't even switch on to begin with.
Absolutely no response. Screen stays pitch black.
I tried doing it with the USB cable in, same result. Nothing.
I also read up on the different combinations to get into download mode to no avail.
Stock ROM and firmware installed, no mods whatsoever.
Android 8.0
Can anyone please suggest anything I can do to save my device?