When I'm in stock rom, auto rotation, auto brightness & sim card doesn't work. Maybe sensor problem.
But when I use custom rom , they works perfectly. I searched on internet and found that sensors are related to persist.img . So can I flash persist.img of custom rom on the stock one? Custom rom is android 10 & stock is 8.0.
Tawsif999 said:
When I'm in stock rom, auto rotation, auto brightness & sim card doesn't work. Maybe sensor problem.
But when I use custom rom , they works perfectly. I searched on internet and found that sensors are related to persist.img . So can I flash persist.img of custom rom on the stock one? Custom rom is android 10 & stock is 8.0.
Click to expand...
Click to collapse
This doesn't make sense. Have you tried flashing stock rom the official way? Perhaps you missed something.
Fytdyh said:
This doesn't make sense. Have you tried flashing stock rom the official way? Perhaps you missed something.
Click to expand...
Click to collapse
Obviously! My device is moto e5. I used "Rescue & smart assistant tool" from official lenovo website(Motorola was owned by lenovo). That tool detected my device in fastboot & downloaded the official firmware automatically, also flashed it. Before using that tool , stock ROM was fine. Actually I used it to go back to stock condition. So I lost my first ROM(Sensor working one), and there is no way to get it back.
I also tried clean flash(By wiping the system, vendor,data etc. & trying again). That didn't help. Then I tried flashing the ROM with commands in platform tools. Still that issue.
This device is 2 GB ram. So lenovo people don't care. But It's my daily driver (As I'm 14)
Tawsif999 said:
Obviously! My device is moto e5. I used "Rescue & smart assistant tool" from official lenovo website(Motorola was owned by lenovo). That tool detected my device in fastboot & downloaded the official firmware automatically, also flashed it. Before using that tool , stock ROM was fine. Actually I used it to go back to stock condition. So I lost my first ROM(Sensor working one), and there is no way to get it back.
I also tried clean flash(By wiping the system, vendor,data etc. & trying again). That didn't help. Then I tried flashing the ROM with commands in platform tools. Still that issue.
This device is 2 GB ram. So lenovo people don't care. But It's my daily driver (As I'm 14)
Click to expand...
Click to collapse
Have you tried this custom rom?
https://forum.xda-developers.com/t/...-rom-for-moto-e5-play-james-xt1921-5.3806530/
If it works on this custom rom as intended, I would say it is a pretty good guess that this ROM persist image would be compatible with your original version of the stock rom.
Fytdyh said:
Have you tried this custom rom?
https://forum.xda-developers.com/t/...-rom-for-moto-e5-play-james-xt1921-5.3806530/
If it works on this custom rom as intended, I would say it is a pretty good guess that this ROM persist image would be compatible with your original version of the stock rom.
Click to expand...
Click to collapse
That stock ROM will hard brick my device. Because that's for "play" variant. And my model number is XT1944-6 (Rare one). But yeah, I will download the stock ROM from outside the official tool. Thanks for the idea. But 1 question, can I flash rom of another build number? Because in internet, my device's stock ROM build number has 3 at last. But my build number's last digit is 6.
Related
Ok, this is weird, a while ago i didnt had any problems installing any kind of custom rom, used CWM while wiping everything... eveything was OK, ROM worked OK, etc... But one time i installed a ROM (Slimkat) and i lost signal, tried to use my recovery of stock android but it didnt work, so i tried a lot of things untill i got bootlop without being able to install anything since some files were missing, bad luck
After that, i just reflash stock 4.3 and upgrade from there 4.4.2, everything fine again... except that i cant install any kind of ROM, every ROM says "installation succesful" but everyone is stuck into bootloop.
While i havent tried ALL ROMS i have tried the same ones i was using (Nexus G+, LiquidSmooth and CM11), so i guess this problem is coming from my device.
On a side note, i tried to factory reset, but no luck... it shows the Android working but it inmediately turns the screen off, and then it shows it again and then off again... in an infinite loop
Same problem!
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Liberr said:
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Click to expand...
Click to collapse
Hmmm... Pay attention to which version of Bootloader you are using.
You might want to try both 4.3 and 4.4 to see which one would work.
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Good luck!
neozen21 said:
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Liberr said:
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Click to expand...
Click to collapse
Hmmm.. I see there is a version number on mine, 41.05 dated 2013-12-06, but I'm not sure if that's the version or not.
And yeah... if changing the bootloader doesn't help, you probably would have to restore from the stock image and start over..
Got root and custom roms working after I 1.) downgraded to 4.3 and 2.) flash TWRP (instead of CWM).
So I'm not sure what the problem was. Besides the two main rooting methods (superboot and custom recovery), there are some other methods described on the forum specifically for people who already did a international variant OTA to 4.4.2. and one that is absolete (here) but apparently works for some when the two main methods fail.
However I'm still not sure if this solved everything. I am not sure if I can flash Cyanogenmod (which is 4.4.2) over a 4.3 firmware. Maybe I need to manually flash a 4.4.2 radio or something... Gonna check that out next...
EDIT: No need to downgrade. Not sure how it works but two main root methods (superboot and custom recovery) didn't work for me. Somehow I got stuck in boot animation. Just installed TWRP instead of CWM after Kitkat firmware (EU Retail) and rooted (/installed Super Su) from there. Everything works fine now.
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
muqy said:
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
Click to expand...
Click to collapse
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
chairsz said:
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
Click to expand...
Click to collapse
Hey man, worked a charm thanks!
For users who may have the same problem:
After flashing 4.3 onto the device it did NOT boot.
- However I then went into the bootloader flashed custom recovery, I used cwm.
- Then I went into recovery, used adb to push the rom and gapps onto sdcard
- Full wipe and then installed rom. Then installed gapps
Working fine.
Cheers chairsz :good::good:
Phone restarts after uninstalling app
I wiped dalvic-cache ,flashed new ROM flashed different gaps but problem isn't solved
I was on kk previously now on 5.1 custom rom
Tjsdj said:
Phone restarts after uninstalling app
I wiped dalvic-cache ,flashed new ROM flashed different gaps but problem isn't solved
I was on kk previously now on 5.1 custom rom
Click to expand...
Click to collapse
Hi!
I have the same problem, ever since i think when upgrading from kitkat to lollipop.
My model XT1033 - Bootloader 41.18 - Rom 12.1-20150815-NIGHTLY-falcon (latest official nightly)
I don't have any solution. I've been using a third-party uninstaller apk that allows just deleting the app's files instead of going through the normal package manager system.
Any advice appreciated
EDIT: I think this problem is the same as http://forum.xda-developers.com/moto-g/help/2-problem-remove-app-systeme-crash-t3070609/ .
i got solution
cGGmzPw said:
Hi!
I have the same problem, ever since i think when upgrading from kitkat to lollipop.
My model XT1033 - Bootloader 41.18 - Rom 12.1-20150815-NIGHTLY-falcon (latest official nightly)
I don't have any solution. I've been using a third-party uninstaller apk that allows just deleting the app's files instead of going through the normal package manager system.
Any advice appreciated
EDIT: I think this problem is the same as http://forum.xda-developers.com/moto-g/help/2-problem-remove-app-systeme-crash-t3070609/ .
Click to expand...
Click to collapse
flah stock kitkat firmware via adb side load it will restore stock bootloader ,it works:angel:
Tjsdj said:
flah stock kitkat firmware via adb side load it will restore stock bootloader ,it works:angel:
Click to expand...
Click to collapse
But i want to use Lollipop (CM12.1), is this still possible with a KK bootloader?
yes get twrp recovery u can install any rom
I've had this problem when I flashed from 4.3 to 5.1.1 AOSP
Security tab in Settings was crashing too
I solved this problem when I flashed stock Lollipop, did first setup, wipe cache/dalvik... (factory reset in TWRP recovery), flashed 5.1.1 AOSP
Use the correct kernel for ROM , Where make changes ( Install ROOT , flashing ZIP , Change Components of ROM) , always use Clear ALL / Factory Reset
And always use updated versions of ZIPs (Kernel , Firmware, Root , ETC .. )
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Update
randyesh said:
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Click to expand...
Click to collapse
Update: It seems as if older ROMs can be installed with no issues. I got a copy of Cyanogen 12 and it installed perfectly and works fine. However, trying to install new ROMs still give issues. Don't know if I am missing something here and/or someone had a similar previous experience.
Can I install ROM from Cool1 on LeRee Le3? I was looking for custom rom for LeRee Le3 and I didn't find. This phone works very slow on stock ROM. I have Letv X526 with the same parameters and it works fastly.
Poziomek said:
Can I install ROM from Cool1 on LeRee Le3? I was looking for custom rom for LeRee Le3 and I didn't find. This phone works very slow on stock ROM. I have Letv X526 with the same parameters and it works fastly.
Click to expand...
Click to collapse
No one who didn´t try can answer you for sure.
As a rule No 1 you can´t flash a rom from other device onto a similar not even almost identical device.
Stock roms contains critical files from sensitive partitions that can perma-brick your device but with custom roms could be slightly different although a kernel from other device can soft/hard brick yours.
Despite you could install it you may expect a lot of issues cause it was builded for other device.
Said that if you want to take the risk you need to do the next before:
- Backup most important data.
- Download a stock/factory rom for your device if you need to restore it.
- Unlock bootloader.
- If you are going to flash a stock rom, flash only system, userdata partitions and the boot image you need to port it and keep the same kernel to avoid brick it.
Best you can do is search for a custom rom from a similar device and learn/read and try to port it for your device at least in the case that you can´t build it from the source for various reasons..
-
Yes you can