Hi,
after I restored the backup - TWRP was:
LeEco_X820_MAX_TWRP_v4_CUOCO92
my phone did not boot, stuck prior the colored "EUI" will pop up - 12 mins... several times.
After TWRP->install the rom LeECO_Le2_X820_MAX_5.9.020S_V65_CUOCO92 again it booted fine.
Any idea what can cause this?
BTW: I had to restore as installing Xposed killed somwhow the home screen to start - aleays stopped in loop...
Related
Just a quick question about the boot-up time after the flashing of Gobstopper.
Atrix is rooted, unlocked, tenfars CWM on a stock 2.2.2
Used Rom manager to flash update.zip (after format data/cache/dalvik) and i didn't see any errors and it looked as though it went through. It has been on the boot animation for about ten minutes now.
50% Battery when I started
How long should this first boot take?
if it's looping.. Battery pull -> restore back-up through recovery?
Thanks
**UPDATE: White LED flashing?? Is the battery almost dead now?**
**Update: Booted finally after about a half hour but the digitizer is reversed.
Another update: shutdown -> battery pull -> turned it on.. waited 10 minutes on the boot animation -> F%^& It! -> restoring backup through recovery
Backup restored but the digitizer is still reversed(mirrored)... wtf?.. saw a post about this some where before.. I'll try to find it again
Thanks: http://forum.xda-developers.com/showthread.php?t=1182782&highlight=touch+screen+reversed
Update: on trying to get the fix working for the touch screen I ran into ADB returning "offline" for my phone.
Tried this post: http://forum.xda-developers.com/showthread.php?t=974824
but still getting offline device from ADB... frustrated much? I think so!
Update::
After a bunch of reboots, i tried booting into recovery to try another backup. It didn't start the recovery but went fully into the home screen. Touchscreen now works and I can connect with ADB. I have no idea why it started working. Can anyone shed some light on it?
Well, first of all, there was a fix for reversed touch screen on here somewhere.
Basically, you had to do "Fix Permissions" in CWM as far as I remember.
Second, seems like you had the reversed touchscreen problem because you flashed across different version of Android (2.2.2 <=> 2.3.4). At least that's when I had this problem.
To avoid this you either have to flash via fastboot and do a full wipe. Or do the "fix permissions" thing and also do a full wipe.
Well I thought it fixed itself.. I lost connectivity though and restarted. Once loaded the touch screen was reversed again.
I going to carry on with those fixes I have linked in the OP and hopefully that will fix it permanently.
Update: reinstalled cwm recovery -> boot to recovery -> wipe data/factory reset -> restore backup -> Booted up fast without a problem...
I'll try the 2.3.4 again using the fastboot method later
A couple of nights ago, I accidentally let my phone die. It must have been doing something important, because I kept getting force closes on all stock apps and also apps that required root including superuser. I rebooted to see if that fixed the problem but it didn't boot up after, I figured it wouldn't be a problem and deleted my cache and dalvik and rebooted. The phone booted to the lockscreen saying "Upgrading android, Optimizing x of x applications" but I noticed that when it got to the 33rd app, it would suddenly go very fast and the phone would crash to the boot animation (not the boot logo) on "starting applications". It wouldn't boot back up until I did a hard reboot. After a while, I realized it wasn't going to fix itself and just wiped and re flashed everything. I did restore some user apps in tb and everything was fine. On the next day, i made sure that the battery didn't die but i woke up to the same force closes and bootloop when i rebooted. Tried to delete cache and dalvik again to see if i could reproduce the problem but now it wont boot past the animation at all.
Im using siyah 3.2.7.2 and my second rom (which boots fine) is Pure ics
EDIT: On 3.3.1 now, doesn't make a difference
well
i got an alcatel ot908 3 days ago, i installed clockworldmod recovery and after rooting it, i backed up so i can flash a rom but this didn't worked, rom wasn't working as thephone stucked on the boot screen saying "alcatel one touch" and nothing was happening... so i restrored the backup i had made and everything was fine, yesterday i installed a lot of stuff and i wanted to reset factorysetting so i shutted down the phone and went into recovery screen, i wiped everything but since then the phone stucksagain on the boot screen, tried reseting again to factory settings but nothing, i also wiped cache and other stuff but still won't boot. I tried to restore the backup i already had, the same that i used to restore when i had problem with the rom but it didn't worked. Now for some reason it doesn't even reach the alcatel boot screen, it just shows the android icon and then stucks with a black sccreen and the buttonsenlightened
what do i have to do to get it work again?
I'm using Moto C plus since past 2.5 years. Last week it suddently restarted. I thought it may be an issue of main memory full. So, let it to restart. But it went on a bootloop. I had more than 2GB free in internal storage. Then I wiped cache and tried booting. It booted successfully and then after 5-10 seconds it froze again and restarted and the bootloop continues. I tried wiping all data but no luck. I tried system root integrity check which failed. I flashed stock ROM again and started phone but the same issue continued. It boots successfully, I get home screen and then after 5-10 seconds reboots.
I thought of flashing custom ROM then. I flashed TWRP. While I was flashing zips using TWRP, TWRP itself restarted randomly. I somehow flashed DotOS and Ressurection Remix with GAPPS but same issue existed.
Now I'm back on stock ROM. Sometimes it boots successfully and then after using for 5-10 minutes it randomly reboots and get stuck in a bootloop freezing on Moto logo or Lenovo logo and then restarting.
What could be the issue here? Is there a hardware problem?
Hello,
short background story:
I have a KIW-L21 which is running Android 7.0.1 Resurrection Remix CustomROM. Recently, my battery and power button died, so when I plugged in the phone to charge it, it would immediately power-cycle (button defective and constrantly forced the phone to reboot).
I got both replaced by now, but the phone does not boot anymore (I guess due to the continuous power-cycling maybe some files got corrupted). It will show up the initial RR logo and then the boot animation, but it will not get past that anymore. I haven't flashed or changed anything on the phone for ages.
Bootloader is unlocked and TWRP 3.4.0-0 is installed. I can access the bootloader, TWRP and even the eRecovery by physical button combinations.
Before loading a backup, I'd like to know if there's anything I can try in order to get the phone back running (something similar to chdsk on Windows or the like )?
dmesg.log and recovery.log attached, in case this is of any use. What I can see is that the time and date is totally ****ed up, I highly doubt this would prevent the phone from booting though.....
If nothing else helps and I have to restore a backup, which partitions exactly should I restore? Only boot, data and system as described on the TWRP FAQ? Does it really hurt if I restore further partitions? After all, they're created using TWRP on my own phone, not downloaded somewhere.
Thanks in advance