hello, I have a short time since the problem that the charge of long takes 3-4 hrs
in addition, the problem that 100 are displayed percent in recovery (TWRP), in the in normal running system, only 74
how could this happen? its since few days i dont change any before it works well
i am on newest mahdi rom and hells 44t3
Try flashing the CWM touch and see if it helps.
Can you please give me a downloadlink for latest version of cwm flashable
An best could be a link for flashing bag twpr
Related
Is there a way to flash the stock recovery while retaining my custom ROM?
I've been having battery problems after installing community ROMs which were installed via CWM or TWRP. Basically my battery would last ~36 hours, but would go from 100% to 1% in 12 hours and sit at 1% for the next 24 hours. After a bunch of tests, if figured out its actually caused by having a custom recovery, not the custom ROM. I arrived at this conclusion by flashing CM10 ROM (had battery issue), then back to stock ROM (still had battery issue), then a full stock restore including the recovery (no battery issue.) I've repeated many combinations of these types of flashes using both CWM and TWRP, both cause this same issue to the same extent.
Basically I want to restore the stock recovery while keeping CM10. Since I don't use CWM/TWRP often and can flash it if I do, I'd like to just remove it.
If you have the factory recovery, just flash it the same way you flashed a custom recovery. If you don't have it, you can find it in the factory firmware and use fastboot to flash it.
jjlangen said:
If you have the factory recovery, just flash it the same way you flashed a custom recovery. If you don't have it, you can find it in the factory firmware and use fastboot to flash it.
Click to expand...
Click to collapse
Thanks. I didn't realize it was just sitting in the root directory of the file at http://forum.xda-developers.com/showthread.php?t=2017200 Will update after a full battery drain and charge in case others have this problem.
sototallycarl said:
Thanks. I didn't realize it was just sitting in the root directory of the file at http://forum.xda-developers.com/showthread.php?t=2017200 Will update after a full battery drain and charge in case others have this problem.
Click to expand...
Click to collapse
This does in fact fix my 1% battery problem. So bizarre that a recovery would change the way my battery meters.
Hi friends,
I need help, i have an e612f that i flash an 6610 firmware, works so much good, then i rooted, unlock bootloader and install cleanROM from flatski. Is an amazing firware, but i thinked that was time to change to another, then i choose MIUI. I do the right stuff (wipe data/cache, format system) and the CWM says me that finished, no problems. After it and and before restart, i flash the new kernel from flatski (0.70) and restart.
Phone started MIUI, but it shut down. Every time.
I thinked that the problem could be the kernel, then i flash the 0.23 version. Same shut down happens.
Then i think that the problem could be the firmware, and flash the last Cyanogen build (20130623) and the gapps (20121011). Then restart, and cyanogen keep the boot animation running... running... running... much more than 10 minutes.
Then, this morning i decide flash via kdz the stock of e610, because in my mind, if i mess something, the stock will clean and solve. But i can't do it because i discover that i cannot enter in emergency mode.
Now i give a second chance to Cyanogen, it is running until i i stop. I planning let it run for an hour if necessary, or i get an answer.
In mind mind, the problem was the kernel. I'm right? what can i do now? i can using the CWM, this is a good news. Can someone help me? :good:
nice discover!
i get an error in CWM:
E:can't mount /sdcard
but happyfully, i have and external sd to help me. And ADB installed on my computer.
Any ideas?
hi guys,
my find 5 was having some reboot issues (it was rebooting a few times per day) and that was a bit anoying. I was using an old original FW so i decided to update to a newer one. Heard good stuff about the Omni so i went for that, so i was using TWRP 2.4.1.0 (i think... i'm sure it was 2.4.x) and on the omni page they said we have to use TWRP 2.6 so i went for an update.
here, i think, i've created my problem. I used the new flashify app to install the TWRP but instead of choose recovery img i choosed to flash the boot and i guess i'd flashed the TWRP on the boot.
well anyaway, now i'd installed the TWRP 2.6.3.1 i manage to start the phone in fastboot and recovery all good here, i install every rom nice and easy over TWRP but the phone simply doesn't start, it gets stuck on Touchscreen Firmware Update please wait.... this happens ALWAYS with what version of TWRP or even if i install CWM...
my guess is that i'd messed up some partition or so i don't really know what but i'd tried to format every partition that TWRP let me and still getting the freackin Touchscreen Frim updt screen... so need some Pro help to help me undo the mistake i'd done...
thanks for everything
On the official Oppo forum's there's a guide on how to install the latest Omnirom. Under known issues it says:
5)After installing the TWRP recovery the Screen Touch firmware update goes on for more than 5-7 minutes, do a hard reboot and you would be fine,
Click to expand...
Click to collapse
I haven't tried it myself since I didn't get the problem when flashing Omni and Asylum, but it seems to be worth a shot.
In case you are looking for the topic, search for "How to Install OmniRom 4.4".
Hello all.
I have a Galaxy S5 running cyanogen 13 ( cm-13.0-20161013-SNAPSHOT-ZNH5YAO21L-klte.zip ). Last night I updated it with the cyanogen tool, as usual, thinking that I was just getting a more updated version of cyanogen 13, but apparently I got it working with android 7.1.
As gapps were not working, I downloaded both 7.1 gapps, and cm-13 to try to install gapps or comeback to cm-13 if it did not work.
The problem is that I had no chance to test it. I rebooted the phone with the option "recovery reboot" and after it turned off it showed something like "no command", then it got to the first screen (recovey booting... in blue, samsung galaxy s5 white logo...) and freezed there.
I've tried every key combination and it does change nothing. I've read in another forum an user having the same issue so I advice you to not install this update. At least not from CM13. I will update when I get more details from the other users or if one of us success while trying to unbrick.
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
LGaljo said:
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
Click to expand...
Click to collapse
Hello!
Thank you very much, as I found the problem was the recovery I've re installed TRWP. CM14 was replacing it each time I installed it by ODIN so i had to start it just directly after flashing it (without letting the phone boot) and i've installed last CM14 klte file and 7.1 GAPPs
Now all is working , I hope it can help others with the same problem
Thank you!
Z00LD, ZE550KL
Using since May 2016. Still getting 3.5 hours SOT. Tested many ROM.
Last ROM was AOSP Extended 6.7, Pie. Everything was working well.
Today, I wanted to root my device. So I installed Magisk 20.3 zip via TWRP latest recovery (3.2.3 may be). After installing that zip it was started bootloop. I didn't create any backup. So I made a clean flash the same ROM and GApps(full).
Here, the problem has started. The GApps is not installing properly. Before 100% done, it reboots and bootloop starts.
I used adb and fastboot to go back stock. Everything was done perfectly. But still, boot loops.
Can not find any reason, is it battery problem or others?
Please Help!!!
kowshikkhan.rcs said:
Z00LD, ZE550KL
Using since May 2016. Still getting 3.5 hours SOT. Tested many ROM.
Last ROM was AOSP Extended 6.7, Pie. Everything was working well.
Today, I wanted to root my device. So I installed Magisk 20.3 zip via TWRP latest recovery (3.2.3 may be). After installing that zip it was started bootloop. I didn't create any backup. So I made a clean flash the same ROM and GApps(full).
Here, the problem has started. The GApps is not installing properly. Before 100% done, it reboots and bootloop starts.
I used adb and fastboot to go back stock. Everything was done perfectly. But still, boot loops.
Can not find any reason, is it battery problem or others?
Please Help!!!
Click to expand...
Click to collapse
When phone reboots after stock image flash where you pluged in? if while pluged in booting perfectly and without pluged in boot looping that is kind of battery issue!!