Hey guys,
so my Nexus 5x all of a sudden shut itself down all of a sudden and was stuck in a bootloop (in this case I'm talking about the thing always booting until the Google logo and then restarting itself). Fortunately for me the device was still unlocked (but for some reason I didn't have TWRP installed anmore...) so I tried to install an earlier factory img. Turns out I didn't have enough space on my phone to unpack, so being a smartass I thought 'Hey, locking the device wipes all of my stuff.' Well... Should have thought about how to unlock it again.
Current state is:
1 the phone boots until Google logo and then is stuck (no more rebooting though)
2 when I try to enter Recovery mode it boots until Google logo and then reboots to state 1
3 the device is locked so I can't flash anything from my PC
So does anyone have an idea what's left to do other than smashing the thing against the wall, burning it to ashes and dancing around the fire? I am currently messing around with those instructions
https://forum.xda-developers.com/nexus-5x/help/guide-fix-bootloop-locked-bootloader-t3608679
but it doesn't seem I can unlock the phone from my PC (which was what I guessed but I'm pretty much clutching at any straw now...)
Thanks in advance
Related
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
I had installed CM13 on my Nexus 5. Everything was working fine. Today I woke up to see Nexus 5 won't even get passed to CM android logo when starting. I then tried to go to boot loader. Hopefully, it opened and I navigated to Recovery and opened. But phone also stuck at TWRP logo. I also noticed when phone starts Google logo takes a little more time to disappear than before. I waited a lot for this but it stuck forever. Actually phone was in charging but battery connector was removed when I saw it in the morning. So it kept rebooting at Google logo. I don't think that could be an issue as it already happened before.
Now all I care about is my data. If I flash TWRP using fastboot, will it work? Will my data be removed? Please reply as soon as possible. I am so concerned about this. Thank you
It might be a little Late but yes you should be able to flash a fresh recovery..without loosing your data
Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.
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.
Hi all, first of all I'd like to apologize for my dumb questions (if I make any) and for if I'm posting in the wrong place, kinda new in here.
I explain my situation: I had a hardbricked X820 (I don't remember how it got bricked because it was like one year ago but I think it is a matter of hardware because I think I remember it fell off from such a high place, don't know yet and that's why I made this thread) and I followed quite a lot of guides (A LOT) and it seemed that the only working method was using FlashOne tool with QFIL files. It seemed everything went well until it finished the flashing process. After booting up the device it happens nothing, and sometimes I see the booting logo of LeEco followed by what it seems a shut-down with blinking red led. It sometimes aswell appears the blue led when booting into system and also when trying to boot to recovery. Fastboot mode works fine btw.
I have already spent more than 20 hours trying to fix this, but all I got is:
- device can already boot after following this guide (before I got nothing but red led light when trying to boot)
- device boots but wether:
It stucks in the booting logo
screen turns off and blue led appears
screen turns off and a blinking red led appears
- can't boot into recovery, even by booting an image from fastboot mode. Recovery booting screen doesn't even display and blue led appears again
- fastboot mode is fine and the device is recognized by the computer
I first thought it was that some hardware was causing the issue because of the fall but after seeing it can communicate with the computer and boot into fastboot mode I don't think it's a matter of hardware... But still I wanted to consult you expert guys
I'm a bit fed up and out of ideas... What can you guys come up with? I really need help. I'm completely stuck.
I might have (for sure) forgotten to give more relevant info so don't hesitate to ask!
Thanks a lot in advance!
If you like you phone and If nothing work, I hard brick a kindle fire 6 hd and replace the motherboard that I found for cheap and the tablet is back and working like new.
MikeViller said:
If you like you phone and If nothing work, I hard brick a kindle fire 6 hd and replace the motherboard that I found for cheap and the tablet is back and working like new.
Click to expand...
Click to collapse
That's a good idea! But I've been seeking cheap mobos and I can't find any... I'm very poor and I can't afford buying new hardware for a device I'm not using daily, that's why I wanted to know if the issue was about hardware, something I see clearer every time... :crying: :crying:
didiloro said:
Hi all, first of all I'd like to apologize for my dumb questions (if I make any) and for if I'm posting in the wrong place, kinda new in here.
I explain my situation: I had a hardbricked X820 (I don't remember how it got bricked because it was like one year ago but I think it is a matter of hardware because I think I remember it fell off from such a high place, don't know yet and that's why I made this thread) and I followed quite a lot of guides (A LOT) and it seemed that the only working method was using FlashOne tool with QFIL files. It seemed everything went well until it finished the flashing process. After booting up the device it happens nothing, and sometimes I see the booting logo of LeEco followed by what it seems a shut-down with blinking red led. It sometimes aswell appears the blue led when booting into system and also when trying to boot to recovery. Fastboot mode works fine btw.
I have already spent more than 20 hours trying to fix this, but all I got is:
- device can already boot after following this guide (before I got nothing but red led light when trying to boot)
- device boots but wether:
It stucks in the booting logo
screen turns off and blue led appears
screen turns off and a blinking red led appears
- can't boot into recovery, even by booting an image from fastboot mode. Recovery booting screen doesn't even display and blue led appears again
- fastboot mode is fine and the device is recognized by the computer
I first thought it was that some hardware was causing the issue because of the fall but after seeing it can communicate with the computer and boot into fastboot mode I don't think it's a matter of hardware... But still I wanted to consult you expert guys
I'm a bit fed up and out of ideas... What can you guys come up with? I really need help. I'm completely stuck.
I might have (for sure) forgotten to give more relevant info so don't hesitate to ask!
Thanks a lot in advance!
Click to expand...
Click to collapse
Follow this guide using pc
https://www.google.com/amp/s/www.******.com/install-twrp-root-le-max-2/amp/
Once your phone booted into twrp recovery, your phone is alive.
Download twrp 3.2.3-1-x2 and custom rom and save in otg drive for recovery flashing.