OK I had an issue awhile back where my phone really took a crap. Not sure what happened, it is not rooted. But it would not boot, would just go to a dead android. No recovery, nothing. So 2 days of playing around with different programs, I finally got it to boot normally and all seemed well. Now I got a message for a new update and it reboots and does nothing. If I check for updates it downloads it again and does the same thing.
So I tried to boot to recovery and I don't have a recovery now. I get to the fastboot screen(I think that's what it's called) and select recovery. Just reboots. I connected to my laptop and issued the adb reboot recovery, same thing, just reboots. Adb reboot bootloader works however.
So if I have no recovery, how do I re install the recovery? I'm to the point where I might just buy a new one, as fast charging doesn't even seem to work anymore but I'd rather not, I really like this phone.
Thanks for any help you can give.
I believe if you download the proper firmware for your phone, you should be able to extract the recovery image and flash it through ADB. ( fastboot flash recovery recovery.img). As long as you have Asus drivers and ADB installed, you should be able to. I'm sure this is how I reflashed my recovery after I accidentally wiped it.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Thanks Quicksilver, I'll give that a try. I was a lot more up on all this stuff a few years ago when I used to root every device I got. I've been happy with the stock Zenfone 2 so I haven't messed around with this stuff for a long time!
You're welcome Bluze. I hope this for you.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
That didn't work. It seemed to flash recovery.img ok, but still no recovery mode.
Wow, I don't know what exactly worked but I have a recovery now. I finally just bit the bullet and unlocked the bootloader, then used a tool that supposedly roots and installs Clockworkmod. Well, it didn't work. Sort of. I was able to get to cwm recovery one time before I rebooted but it was all back to "normal" (no recovery and not rooted). Rom Manager would hang when I tried to reboot to recovery. So I downloaded SuperSU and installed it manually. Ta Da! Root! Tried to reboot to recover and dead android. Pressed power and volume up and for the first time, it rebooted to stock recovery! Still no CWM, and I'm not sure it will work on Zenfone 2 but hey, I got my recovery back! Now I won't be able to do OTA upgrades but at least I can do them manually!
Quicksilver, your suggestion should have worked. It didn't, but thanks for the help!
Related
After I was presented with a system update about a week ago my nexus s entered a boot loop, not knowing why I tried to restart it a couple of types via removing the battery. That didn't work so I entered the Fastboot mode and tried to go into recovery but I couldn't do that because I was then presented with a exclamation mark like picture on my Nexus S, My phone was rooted before because I wanted to install Miui rom, then when I went back to stock rom and everything seemed to work fine, but when I tried to change my rom again it said I wasn't rooted but on my bootsceen it says I'm unlocked. I also did a permission test, from here I don't know what to do if anyone could help me I'd be very grateful.
BumpBumpBump
Flash clockwork recovery, through fast boot.
restore or flash new rom
Sent from my Nexus S using XDA Premium App
Alrighty, I flashed Clockwork recovery, now thats left is to flash another rom.
So I am fairly new to rooting and didn't know that it's not a great idea to do an OTA update while you're rooted. So I did just that and when prompted to restart the phone, it did and loaded directly in to TWRP. I tried to just reboot from there and it kept going back to TWRP. So I tried to recovery from a backup, same thing, right back to TWRP. Also, I can't get into download mode. What do I do?
floydmcscroops said:
So I am fairly new to rooting and didn't know that it's not a great idea to do an OTA update while you're rooted. So I did just that and when prompted to restart the phone, it did and loaded directly in to TWRP. I tried to just reboot from there and it kept going back to TWRP. So I tried to recovery from a backup, same thing, right back to TWRP. Also, I can't get into download mode. What do I do?
Click to expand...
Click to collapse
This should help. http://forum.xda-developers.com/showthread.php?t=2451696
You need to first download the kdz and lg flash utility with drivers.
Install drivers
The factory reset deleting system, cache, internal sd.
Then shutdown your g2.
Start to downloaded mode connecting your g2
Flash kdz & voila... Done
I too bricked my phone before. My flashing stuck at 49%. Recovered using above method, all is well now
This works 1000%. I bet on it. Just remember to wipe the phone completely before flashing. You will return to stock with unrooted status in download mode. U will have your warranty back too
Sent from my LG-D802 using XDA Premium 4 mobile app
Hopefully someone can help. There was an update on Google Play today for the Chainfire SuperSU. I ran the update, clicked the message that I needed to update the binary, chose TWRP (I'm on 2.8.7.0), and the phone rebooted. After booting, it went into recovery, tried to run something (I wish I had written it down), and rebooted again. It did this again and again, looping about 10 times before I finally held the power button. At that point, the phone tried to boot normally, but never went past the boot animation (waited about 30 minutes).
I can still get into recovery, luckily... I just don't know what I should do at this point. I am running the stock MM, just debloated.
From which SuperSU version did you run the update?
Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
I was able to fix the issue by booting into recovery, copying the latest supersu zip to internal storage via MTP, and installing the zip manually. Once that was done, the phone finally booted all the way.
andry23jsv said:
From which SuperSU version did you run the update?
Click to expand...
Click to collapse
The update was from the newest one in the store. It came up just like any other app update does. The funny thing is, when I went back to look at the latest version in Play, it was definitely older. I wonder if it was pulled.
jason2678 said:
Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
Click to expand...
Click to collapse
I had tried all that. It's usually the first thing I do when I have issues like that.
Hey, i am using a note 4 . Currently my phone is in recovery mode and is boot looping. It would boot for 2 secs then reboot again. i cant exit the recovery mode at all the clear any cache or stuff. I may have misclicked the normal boot and clicked the TWRP after updating supersu. Is there a fix for it?
Did you try manually copying the latest SuperSU zip file to your internal storage (via MTP, or adb), then installing it from recovery?
Flapjack said:
Did you try manually copying the latest SuperSU zip file to your internal storage (via MTP, or adb), then installing it from recovery?
Click to expand...
Click to collapse
hi the problem is that i cant get pass the recovery mode. its there for about 2 secs then gone
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?
Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.
Flapjack said:
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?
Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.
Click to expand...
Click to collapse
Hey man tks for replying so promptly though. I think i know what went wrong. Just that i don't know how to fix it. My phone is now recovery booting through TWRP. But i don't remember having TWRP. Is there a way to change the boot to normal?
I can't reboot to Recover on my OP2, tried to do a backup but couldn't reboot to recovery. I was on Skydragon 3.4 then flashed the Stock 2.2.1, clean, 3 weeks back - I was able to access the recovery till last week but dont know what happened.
Help please.
Basit Hassan said:
I can't reboot to Recover on my OP2, tried to do a backup but couldn't reboot to recovery. I was on Skydragon 3.4 then flashed the Stock 2.2.1, clean, 3 weeks back - I was able to access the recovery till last week but dont know what happened.
Help please.
Click to expand...
Click to collapse
Try with:
- Reboot Menu Widget
I tried to reboot to recovery didn't work, it shows black screen and remains stuck their, I tried to re-root my phone using oneplus2 toolbox, after running the bootloader unlock, my phone is not turning on, only going to FAstboot mode. I cannot root it even though oem unlock and usb debug was allowed, now I am stuck its not letting flash recovery or rom.
please help
Don't need to root again (root is for the ROM) your ROM or partitions are messed up, flash fastboot image without data partition using naman's ubrick guide
Sent from my ONE A2005 using Tapatalk
Wrong TWRP for your bootloader.... Come on people, start reading before doing ?
I was running cm12.1 a while ago, and updated to cm13. It broke one of my apps that i used on a regular basis at the time, so i tried downgrading back to cm12.1. The OS rebooted into twrp, but nothing happened. I rebooted but it wouldn't let me out of twrp/fastboot/download mode.I tried wiping the data and re flashing cm12.1, nothing. same issue. I downloaded a different custom recovery (a version of clockwork mod) but i believe it was in the wrong format and when i tried to overwrite my recovery with this other one in twrp, my phone stopped booting into recovery at all, and only download mode or fastboot, besides bootlooping when plugged in and not holding any volume buttons or power. The nexus 4 itself IS unlocked and rooted, and was working fine before this happened. I don't know what to do, and i hope someone can help me.
orionboughton said:
I was running cm12.1 a while ago, and updated to cm13. It broke one of my apps that i used on a regular basis at the time, so i tried downgrading back to cm12.1. The OS rebooted into twrp, but nothing happened. I rebooted but it wouldn't let me out of twrp/fastboot/download mode.I tried wiping the data and re flashing cm12.1, nothing. same issue. I downloaded a different custom recovery (a version of clockwork mod) but i believe it was in the wrong format and when i tried to overwrite my recovery with this other one in twrp, my phone stopped booting into recovery at all, and only download mode or fastboot, besides bootlooping when plugged in and not holding any volume buttons or power. The nexus 4 itself IS unlocked and rooted, and was working fine before this happened. I don't know what to do, and i hope someone can help me.
Click to expand...
Click to collapse
Follow this and flash the factory images: https://www.youtube.com/watch?v=uO7HkTrRzwM
Nitin
Thanks for the quick response, i will try to follow that tutorial.
I just want to state that if anyone has the same problem as me, I found a way to fix it
https://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
that nice little tutorial there saved me