Hi,
I have Moto E Condor. I tried to install some custom ROM and I have TWRP. I do not know what happened but my touch screen does not work after successful boot. It does work as long as I have TWRP active. It allows me to install ROM as well. I even tried to install the stock ROM but no good. Touch is new and working.
Please let me know if you can help this.
Thanks
Related
hi ..i have a Moto E XT1022 Dual Sim Indian Phone(4.4.4 Kitkat STOCK)
REcently I had unlocked and even rooted my phone by Flashing CWM 6.0.5.0 and Super User 2.46
Later when i tried flashing 5.1 Lollipop! Tried Blisspop then Minimal OS
It seems to Bootloop
I mean that it Stays in Boot Animation and when i press power off it reboots automatically
can some one tell me where i went wrong?OR what i can do to Come out of this Mess!?
POOSIBLE ERRORS I FEEL:
1.)Not installed SDK
2.)not installed Busy Box
benishere said:
hi ..i have a Moto E XT1022 Dual Sim Indian Phone(4.4.4 Kitkat STOCK)
REcently I had unlocked and even rooted my phone by Flashing CWM 6.0.5.0 and Super User 2.46
Later when i tried flashing 5.1 Lollipop! Tried Blisspop then Minimal OS
It seems to Bootloop
I mean that it Stays in Boot Animation and when i press power off it reboots automatically
can some one tell me where i went wrong?OR what i can do to Come out of this Mess!?
POOSIBLE ERRORS I FEEL:
1.)Not installed SDK
2.)not installed Busy Box
Click to expand...
Click to collapse
Well by I know you can't install a Lollipop rom using kitkat on motorola..try flash cm11 or some based rom on KitKat and see if it works Or update your device to soak before change the rom to some lollipop/cm12(.1) based rom.
Hey guys.
I have a moto e XT1022. I flashed cyanogenmod 13 on my phone and the process completed without any errors. But when I rebooted my phone it's stuck on the cm logo. please help. Can I go back to the stock ROM in any way? I used TWRP 2.8.5.0
aditya487 said:
Hey guys.
I have a moto e XT1022. I flashed cyanogenmod 13 on my phone and the process completed without any errors. But when I rebooted my phone it's stuck on the cm logo. please help. Can I go back to the stock ROM in any way? I used TWRP 2.8.5.0
Click to expand...
Click to collapse
Flash the Stock ROM zip file from recovery. Search for XT-1022 Stock ROM debloated...Dowload it and flash it.
Hit Thanks if I Helped!!!!!!!!!!!!!!!!
i had cm 13 installed in my moto e condor. i did a OTA update of a nightly ( i do not remember the version ) about a month ago but since then it is not booting. it just shows the cyanogen logo on the screen and it goes on and on.
i tried the recovery through adb but it is not able to access my sd card where the recovery is installed.
am i doing something wrong ??? i am not a technical person but i find rooting and installing custom roms thrilling.
it is not my main phone. just a side kick. so not worried too much. but if someone can help may be it will help me in understanding this rooting and installing custom roms process more.
rajesh.rajkot said:
i had cm 13 installed in my moto e condor. i did a OTA update of a nightly ( i do not remember the version ) about a month ago but since then it is not booting. it just shows the cyanogen logo on the screen and it goes on and on.
i tried the recovery through adb but it is not able to access my sd card where the recovery is installed.
am i doing something wrong ??? i am not a technical person but i find rooting and installing custom roms thrilling.
it is not my main phone. just a side kick. so not worried too much. but if someone can help may be it will help me in understanding this rooting and installing custom roms process more.
Click to expand...
Click to collapse
CM13 had bootloop bug in last few nightlies. So u better install other ROM or try cm14.1
Ujwal Agrawal said:
CM13 had bootloop bug in last few nightlies. So u better install other ROM or try cm14.1
Click to expand...
Click to collapse
Thanks Ujwal. appreciate your help. but at present it is not accessing my sdcard because of this bug. so nothing happens after i select recovery option in boot loader screen. so i may not be able to flash or clear cache or anything. can you please guide me how to install any newer rom or i might even install the stock cm13 which is still with me and was working fine till i installed the nightly update. please explain me how to install back cm 13 or any newer rom, please.
Could you go to twrp?
Have you tried to flash twrp using fastboot?
Hi there. I'm using Redmi Note 3 SD from quite some time. I've officially unlocked the bootloader and flashed many custom as well as MIUI Roms from time to time. But recently I'm facing a problem. I'm trying some Nougat based Roms but facing a weird problem. After flashing Rom when the phone boots up and setup screen comes than while setting up the phone screen crashes in some certain point and it starts from the beginning, it won't past the setup screen. I tried many Roms like NOS, AEX, Lineage but facing the same problem. I've used Nougat based Rom previously but was not facing this issue, it only started when i tried to flashed newer build. Am I doing something wrong. Please I need urgent help so any help will be highly appreciated.
Are u trying to flash the 7.1.2 based rom with 7.1.1 gapps.If yes then first flash the rom and boot, there will be no setup wizard this time and then flash the gapps
ShivamTiwari said:
Are u trying to flash the 7.1.2 based rom with 7.1.1 gapps.If yes then first flash the rom and boot, there will be no setup wizard this time and then flash the gapps
Click to expand...
Click to collapse
I tried without Gapps too but at a point when it ask install from backup or start as a new device it crashes no matter whichever option I choose. Any idea whats the reason. Thanks
rjrulz007 said:
I tried without Gapps too but at a point when it ask install from backup or start as a new device it crashes no matter whichever option I choose. Any idea whats the reason. Thanks
Click to expand...
Click to collapse
Well in that case, I have no idea.Sorry bro,wait for someone else to reply.
rjrulz007 said:
Hi there. I'm using Redmi Note 3 SD from quite some time. I've officially unlocked the bootloader and flashed many custom as well as MIUI Roms from time to time. But recently I'm facing a problem. I'm trying some Nougat based Roms but facing a weird problem. After flashing Rom when the phone boots up and setup screen comes than while setting up the phone screen crashes in some certain point and it starts from the beginning, it won't past the setup screen. I tried many Roms like NOS, AEX, Lineage but facing the same problem. I've used Nougat based Rom previously but was not facing this issue, it only started when i tried to flashed newer build. Am I doing something wrong. Please I need urgent help so any help will be highly appreciated.
Click to expand...
Click to collapse
try clean flashing.
download latest gapps first
in case u get bootloop, download this- unlock_bootloader.zip
clean dalvik+data+system+cache,
then flash firmware+rom+unlock_bootloader.zip+gapps
(i'm using twrp 3.1.0.0 official by TheStrix, never faced such problem. follow my method mentioned above)
rjrulz007 said:
Hi there. I'm using Redmi Note 3 SD from quite some time. I've officially unlocked the bootloader and flashed many custom as well as MIUI Roms from time to time. But recently I'm facing a problem. I'm trying some Nougat based Roms but facing a weird problem. After flashing Rom when the phone boots up and setup screen comes than while setting up the phone screen crashes in some certain point and it starts from the beginning, it won't past the setup screen. I tried many Roms like NOS, AEX, Lineage but facing the same problem. I've used Nougat based Rom previously but was not facing this issue, it only started when i tried to flashed newer build. Am I doing something wrong. Please I need urgent help so any help will be highly appreciated.
Click to expand...
Click to collapse
Flash by formating (not wipe) in twrp
Try clean install. Wipe data and system after backing up.
If that doesn't work, Check if any software is making that issue. In my case, not exactly same, but was stuck on boot after flashing super su.
When i tried to flash twrp using flashify. It didn't work for me. My recovery not working anymore. Fastboot not detecting my phone. What to do now to flash recovery??
Try using BeansGapps
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Don't flash a different kernel, just try RR first, boot and make sure it works.
Once that is done, then you can try flashing the kernel and see if everything works. If it doesn't, you have your answer.
Most custom ROMs are also builded just for their kernel so if u flash custom kernel then there is chance that ROM will not work as u expected. Just think about it when you are installing a custom kernel.
Today I did flash lite mode rom . It boots up but touch was not working...nothing was flashed even gapps.
Sometimes the recovery twrp too does not work.,touch lost. Now i suspect something wrong with the hardware.
But no issues with miui roms...Thats what makes me wonder
did you do it on the computer?
sibikallikkat said:
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Click to expand...
Click to collapse
You may want to try installing Radon Kernel. I've got an aftermarket display which also didn't work with a custom rom (Lineage OS), but after flashing Radon Kernel it worked flawlessly. You may want o try Radon 5.0 as I'm having trouble with 5.1.