My CWM Recovery randomly just turns the tablet off and reboots itself. I am on v6.0.1.9. It didn't used to do this until I installed the CWM Recovery App and had it update the version that was on it.
This happens randomly whether it is installing a ROM or just simply sitting there in recovery. Please help as I am worried I am going to corrupt something sooner or later, especially when updating the kernel
Switch to TWRP.
Related
After installing the update every time I try rebooting the phone it reboots into recovery mode and there is nothing to my knowladge that I can do. I saw the solutions for TWRP, but unfortunately I have installed CWM. My phone is only rooted and I haven't flashed any custom ROM.
PLEASE HELP!
I have run clockworkmod alongside CM11 for some time but i decided to install the touch version of CWM from Rom Manager. After the install I hit the restart into recovery button but every time the phone attempts to start it gets no further than the recovery booting screen, crashes and the phone restarts only to do it again. I cannot break this loop. All I want to do is get back to CM. Any suggestions?
sam.hinsley said:
I have run clockworkmod alongside CM11 for some time but i decided to install the touch version of CWM from Rom Manager. After the install I hit the restart into recovery button but every time the phone attempts to start it gets no further than the recovery booting screen, crashes and the phone restarts only to do it again. I cannot break this loop. All I want to do is get back to CM. Any suggestions?
Click to expand...
Click to collapse
Reflash your recovery. It'll fix whatever happened.
radicalisto said:
Reflash your recovery. It'll fix whatever happened.
Click to expand...
Click to collapse
Thanks. Managed to get into download mode and flashed a new recovery using odin
I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
Update: I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.
Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.
Hello,
I have an i9505 LTE International version (jflte) for about 4,5 years, working perfectly with the latest LineageOS until yesterday when my phone suddenly shut off itself (as like as I removed the battery). I tried then to turn it on again but restarted itself after the LineageOS logo appeared. I thought there was something wrong with the OS, so I've booted to recovery TWRP to flash the same OS again. The strange thing is that TWRP stopped flashing at +/- 20% freezing itself. After that I was not able to boot to recovery anymore.
I removed the battery, SIM card and microSD for about three hours. Tried again only with the battery and was able to install LineageOS again. After booting with the fresh installed LineageOS (I formatted the /system /data /cache partitions) the system was very unstable and slow. After 10 seconds the screen went completely pink and it shut off again and never came up (showing me the boot logo and rebooting - bootloop).
I removed the battery again and tried to flash, after one day, with odin the stock firmware. I had no issues while flashing but the OS won't boot. Therefore I flashed the TWRP to the recovery partition and it doesn't work. After 10 minutes without the battery I am able to boot TWRP but when I try to, for example, copy the logs to /data TWRP freezes and I cannot do anything else but hard reboot.
Someone knows what's going on here? Could the eMMC be seriously damaged/corrupted?
The strange thing is that, without the battery for 10 minutes plugged in, I am able to boot to TWRP and navigate through the menu - although after trying to format the /data and /cache partitions TWRP freezes. After a reboot I cannot boot to recovery anymore (it remains stuck on the samsung logo screen with the RECOVERY BOOTING and Set Warranty Bit: recovery headings.
My fathers old S4 has a similar issue, https://forum.xda-developers.com/galaxy-s4/help/s4-i9505-wont-past-screen-boots-t3810088
It seems so strange, I'm currently trying to get the files left on the phone safely of but it crashed when trying to do so and now I can't enter recovery.
But I'm trying to troubleshoot it as good as possible without risking loosing the files, and the strange this is that many S4s seems to have problems with the fact that it is a random restart and then goes into bootloop. But the thing that worries me the most is the fact that you were running Lineage while my father was running stock TouchWiz based on 5.0.1. That leads me to believe that this is a hardware issue, I'm considering unscrewing it and try to troubleshoot it. Going to get my hands on my fathers old extra batteries for his S4 tommorow, will see if that makes a difference.
Did you wipe the /data partition after flashing the stock rom? I had the same issue... After flashing LOS, my phone is bootlooping randomly and i tried to flash stock rom. ODIN does not wipe the data partition after flashing the original stock samsung firmware so the OS can`t boot due incompatible data( The lineage os data with android 7.1.2 is not compatible with lollipop). Try to flash the stock rom again, wait until your device restarts to the robot and hold the vol up+home+on/off to get into stock recovery. Perform a factory reset and then restart. You have to wait a bit (maybe 10 min)
So i started to update viper4android and i accidentally pressed volume up which tries it to install via AROMA now my phone is stuck on bootloop, it just keeps rebooting to recovery trying to install the viper4android, is there any possible way to get out of this or my phone is dead?
Any help will be appreciated,
TIA
a safe haven said:
So i started to update viper4android and i accidentally pressed volume up which tries it to install via AROMA now my phone is stuck on bootloop, it just keeps rebooting to recovery trying to install the viper4android, is there any possible way to get out of this or my phone is dead?
Any help will be appreciated,
TIA
Click to expand...
Click to collapse
You didn't specify your exact phone model, so assuming KLTE
AFAIK aroma does not work well with our TWRP
Can you pull the battery and then boot directly to recovery so you can wipe system/cache/Dalvik and then flash the ROM again?
If recovery is messed up, can you pull battery, then boot to download mode so you can reflash TWRP in Odin/Heimdall, or better yet flash latest stock Rom (caution if you have a g900V/A with stock locked bootloader) in Odin/Heimdall, followed by TWRP?
Post again if you need more help, and try to include as many specifics as possible eg exact phone model, TWRP version, Rom zip filename, Gapps, etc. I'll try to help if I can
I am very sorry for not posting the model number, mine is G900I (KLTEDV), everytime i turn on the phone it just keeps booting onto the recovery and goes to install the viper4android but it fails to do that and reboots again and again, its impossible to do anything basically, not booting onto the rom or anything. Recovery version is TWRP 3.2.2-0, it opens up directly to the zip file which is viper4androidfx-aroma.zip and tries to flash it and crashes and the whole process starts again, pulling the battery didnt break the chain it just keeps rebooting to do that again!
I reflashed a new twrp recovery ver 3.2.3-0, but it still tries to flash that zip file again! Even after deleting the file itself it still tries to flash it and keeps rebooting!
How do i get rid of this twrp loop!? This is so weird!
P.S: After reflashing twrp the phone boots to the rom normally but i cant access recovery anymore, whenever i go to recovery it goes on in an infinite bootloop (cleared cache and dalvik cache using es explorer root), I am also on LineageOs 16.0, tried stock recovery but the stock recovery also keeps bootlooping.
P.S this viper4android is a magisk module!
NVM, solved it by flashing stock rom! Thanks!