Few weeks back had updated to the latest OTA update. Yesterday, I just rebooted my phone as it was little lagging.
To my surprise it just booted into recovery mode!!.
My details:- Stock ROM and Stock recovery, not rooted. Everything is stock.
Things I tried::
1. In recovery mode tried clearing only the cache. Did not help.
2. Download latest official full ROM(1.6GB) and adb sideloaded through the recovery( the option is "Install from ADB->Upgrade android from USB"). ROM get side loaded successfully, but when I try to boot it is the same, the device first asks android pattern, once unlocked it tried to boot the system, but fails and lastly vibrates before rebooting to recovery mode.
Please help me as I have very important files and folders on it. I am completely terrified at this point.
Please advice. Note that I can access fast boot mode and recovery mode.
I resolved it myself by resetting only the "system apps and data" from recovery. Thats a nice option which I never knew it existed!
Related
Hi all,
I'm trying to install Cyanogenmod following techbeasts.com tutorial but I'm stuck at the first step : installingTWRP (or CWM).
I followed precisely all the instructions (I allow debugging mode, I installed samsung drivers, I start the phone in download mode, I connect it with OEM cable, I start Odin, it sees the phone, I select the tar.md5 file.), Odin confirms it went well (green box writing "PASS"), but when I try to boot the recovery mode by holding Volume up + Home + Power it seems to boot another recovery software that doesn't offer a backup or a flashing options: "Android system recovery <3e>"
Can't get it to run TWRP or CWM... Can't install the supersu package.
What I'm I doing wrong? Can someone help?
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
adbhitman said:
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
Click to expand...
Click to collapse
Great it worked, thanks a lot !
But now I'm stuck on the next step : flashing CM11
I rooted my phone, booted TWRP, chose "install>cm11" (the zip downloaded from nova fusion) but it says "failed" after a few sec...
I would post my TWRP log but the forum prevents me doing so...
Well I get few things that you could check first.
1. Do factory reset for example from twrp. Factory reset is needed/recommended before installing custom rom from offical OS.
2. Sometimes just installing fails almost immediately if you have ticked check zip signature.
After you have installed new rom clear cache and davilk cache just in case. I'll do that every time if I install or update custom roms. Also don't forget to install right gapps package after you have installed rom.
Sorry my english and try to understand.
ok just realized i downloaded the wrong cm image (the odin one, not the recovery)
everything running smooth now
Okay happy to hear that everything is fine now. Happy playing with custom roms
Hi, I have a MI5 with chinese ROM...
I've unlocked the bootloader, flashed TWRP rocovery and rooted it.
Problem start when i updated using the built in apps. And now i am in this MI logo screen with the 2 dots flashing... 20-30minutes.
I've tried wiping to factory reset, wipe dalvik > reboot ... no go
I've tried miflash the fastboot rom and Miflash showed "The operation completed successfully." > auto reboot ... now is 25 minutes into the boot.... still no go
I'm panicking now.... Please help
I forgot to mention, the file system is decrypted.
Now i cant go into twrp. there's a screen showing a phone with cable. I still can go fastboot though
Help please
Just to share, I'm able to get it boot again.
Instead of using "Flash All except Storage" in Miflash, I selected "Flash All".
After completion of the flashing, it took around 7-8 minutes for the first boot before system GUI came on.
I think it may be due to SuperSU that i have installed earlier.
But now i cannot boot into recovery, should i fastboot flash TWRP again or revert to stock recovery? Please help on how to do it.
Can i install SuperSU by using fastboot?
it makes more sense now.
After flashing of developer rom, the phone is encrypted again and recovery is reverted to stock which i think will only works with updater.
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
EdrichVerburg said:
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
Click to expand...
Click to collapse
I would suggest that you install the latest twrp with flashify and then update your phone, because the newest twrp has the emui updater already built in, so you don't have to re-flash recoveries all the time.
Thanks Sproker,
One problem though. The lastest twrp does not seem to work because it is EMUI 3.0 and I am on EMUI 2.3?? I recently fixed it finally, but I still want to upgrade to EMUI 3.0... Is it worth it? And if it is, what am I to do?
Download the update.app (B135)
And extract the recovery.img
Now download ADB/Fastboot and the latest driver (HISiute).
Connect your phone with the computer and boot your phone into recovery mode.
Now boot into bootloader mode and search the device with "fastboot devices" if it is correctly connected, it should be displayed.
Now flash (first move the recovery.img into the ADB /Fastboot folder) the recovery.img you extracted before.
"fastboot flash recovery recovery.img"
Now you should have the stock recovery back on your phone.
But if twrp didn't work (erasing cache) the stock will also not work.
Try to erase cache via fastboot. But I don't know the code...
Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.
Hi,
so I was about to flash a new ROM to my Z3C, because I was having some trouble connecting the phone to pc (drivers etc are ALL installed and have beend reinstalled too).
Since my phone was already running on .291, I skipped flashing stock rom, went to recovery, did a wipe, flashed 3.1.1.0 TWRP FOTA Kernel, flashed ROM, booted ROM (fine), forgot to flash GApps, went back to reco... Wait? No more recovery? Hmm.. Let's try booting system. OK! Went to settings and did a wipe. It took me into an older version of TWRP (I don't know exactly, something like 3.0.2.8?!), where I did the wipe myself (Data, Cache, System). I did system wipe because I wanted to flash the 3.1.1.0 FOTA TWRP once again (since it seemed to be incorrectly installed) and then install the ROM freshly. So, after installing TWRP (which was "successful") I tried to restart recovery to install the OS. WHAT? Again no recovery? Damn.. Now there's no more system to boot from.
Then I tried to put the phone into Flash-/Fastboot mode, to install the stock rom and start over again. Trying to Hold Vol+/- while plugging in USB doesn't do sh*t. The green/blue LED pops up for a sec and then disappears instantly. Entering recovery with hardbutton method won't work either.
Now I'm stuck with a phone, that can't do anything.. Is there any way to recover the phone?
I appreciate any kind of help & thanks in advice,
furi
NVM! What 'r the chances of 3 different usb cables being broken? LOL. Sorry for being stupid ._________.