Guys good news our developer sevenmaxs have builded twrp 3.0 for A6000
Here is the link check here Twrp 3.0 for a6000 here
http://lenovo-forums.ru/topic/12713-lenovo-a6000-расширенное-рекавери-twrp-by-sevenmaxs/
thanx man that's what i want
This can be used on a6000 plus or not? Just asking
Ya why nt?
Ya it's worked mate thanks
I got battery indicator bug flashing cm12.1 64bit by satgass and s030 with this recovery. i go back to 2.8.7.7 and its normal.
hezler said:
I got battery indicator bug flashing cm12.1 64bit by satgass and s030 with this recovery. i go back to 2.8.7.7 and its normal.
Click to expand...
Click to collapse
Normal on stock rom a6k+
Whats the battery indicator bug @hezler
Hello!
I'm not quite getting this different recoveries for different Android version
Why this is important and is recovery choosen by which Android version is ON the phone or which Android version I want to install?
For example, I have now stock ROM 4.4.4 but want to install custom ROM like CM or Resurection.
Which recovery I should install and is it just flashing recovery img without bootloader unlocking or such things?
Thanks
Hello all
Im french so excuse my bad english
I was on the hybrid Concept ROM 5.1.1 for ZU then yesterday i've flashed the Résurrection Remix 6.0
When ROM has booted , Google play was not installed
I try to flash another gapps but impossible to have Google play service . Even if i try to install Google play apk , the problem still the same.
So i decide to reinstall another ROM . but i can't because twrp was replaced by CM recovery ans flashing other ROM than 6.0 is impossible....
Does someone can explain me how reinstall twrp or another recovery and go back on 5.1. Custom ROM ?
Thanks to all
ingi28 said:
Hello all
Im french so excuse my bad english
I was on the hybrid Concept ROM 5.1.1 for ZU then yesterday i've flashed the Résurrection Remix 6.0
When ROM has booted , Google play was not installed
I try to flash another gapps but impossible to have Google play service . Even if i try to install Google play apk , the problem still the same.
So i decide to reinstall another ROM . but i can't because twrp was replaced by CM recovery ans flashing other ROM than 6.0 is impossible....
Does someone can explain me how reinstall twrp or another recovery and go back on 5.1. Custom ROM ?
Thanks to all
Click to expand...
Click to collapse
you need reflash twrp recovery 3.0.0 (ex fastboot flash boot twrp-3.0.0-0-togari.img) if you have botloader unlocked
Or use Flashtool
It works fine. Thanx you bro
Flash twrp recovery one more time
Done. Working fine now
Hi, I m having 900T device and I want to know can install this ROM http://forum.xda-developers.com/galaxy-s5/unified-development/rom-tipsyos-4-1-t3393668 and select - Rom klte: TipsyOS Rom v4.x ?
And currently I m on PhoeniX ROM V12.6, so can I simply wipe and install TipsyRom/CM13 or shud I start from the Stock ?
Thanks
I am unfamiliar with Phoenix ROM, but if it is CM based,
you should be able to do a simple wipe and flash it.
If Phoenix is Touchwiz based, I always recommend
starting from scratch. Hope that helps.
Yes Phoenix is TW based and I understood, but I also gave the link and asked which link to follow, klte ? Klteusc ? Etc
I know klte is for g900f but I m bit curious, and want specific advice so I dont brick my device
Sent from my SM-G935F using XDA-Developers mobile app
Hey guys, I am thinking of flashing cm 13 rom based on android 6.0.1 on my moto e (1st Generation). my question is that all you guys who have upgraded to the cm13 rom on their moto e, how is your experience now?facing any problems or is it just great from the stock rom experience. Please help and share.
AbhinavIsgrt said:
Hey guys, I am thinking of flashing cm 13 rom based on android 6.0.1 on my moto e (1st Generation). my question is that all you guys who have upgraded to the cm13 rom on their moto e, how is your experience now?facing any problems or is it just great from the stock rom experience. Please help and share.
Click to expand...
Click to collapse
You will get performance close to deodexed KitKat stock rom .. No problems so far .. surely upgrade your device to cm13 :good:
definitely no problems.. just great.
latest nightly works flawlessly..
there is plethora of feature in marshmallow and in being cyanogenmod
I am also thinking in flashing CM13 rom based on android 6.0.1 on my Moto-E (1st Generation) XT1021...
I am currently using the following 5.1 ROM:
Retail US 5.1 ROM (Optimized) v1.0a (311mb)Non-Deodexed:
http://forum.xda-developers.com/devdb/project/dl/?id=14437
That I Found in the following post:
http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
So, I would like to know if I can safely flash directly the CM13 ROM, on top of my current v5.1 ?
And if anyone here could give me the correct link to download the CM13 ROM that works best on the Moto-E XT-1021 ?
Thanks in advance for helping me !
ulises.rodriguez said:
I am also thinking in flashing CM13 rom based on android 6.0.1 on my Moto-E (1st Generation) XT1021...
I am currently using the following 5.1 ROM:
Retail US 5.1 ROM (Optimized) v1.0a (311mb)Non-Deodexed:
http://forum.xda-developers.com/devdb/project/dl/?id=14437
That I Found in the following post:
http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
So, I would like to know if I can safely flash directly the CM13 ROM, on top of my current v5.1 ?
And if anyone here could give me the correct link to download the CM13 ROM that works best on the Moto-E XT-1021 ?
Thanks in advance for helping me !
Click to expand...
Click to collapse
Yes you can directly clean flash cm13 .. make sure you use gapps 6.0 .. and flash cm13 and gapps in a single session
https://download.cyanogenmod.org/?device=condor
Here is the link to official nightlies
ABSathe said:
Yes you can directly clean flash cm13 .. make sure you use gapps 6.0 .. and flash cm13 and gapps in a single session
https://download.cyanogenmod.org/?device=condor
Here is the link to official nightlies
Click to expand...
Click to collapse
ABSathe, 1000 Thanks for the quick reply, for letting me know that I can directly clean flash cm13 over 5.1 and for the link to official nightlies !
Please confirm if this is the correct method to flash the CM13 ROM:
1) Boot into latest TWRP and Format Data: Wipe > Format DATA > Yes
2) Transfer ROM to SDCARD or Internal Storage: CM13 ROM + gapps 6.0
3) TWRP > Wipe > Factory reset and flash CM13 ROM, and then Flash gapps 6.0 (flash cm13 and gapps in a single session)
4) Reboot.
However, since I have already installed in my Moto-T, the version 2.8.7 of TWRP ( http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879 ), I would like to know if is better and also you recommended me to install first ( using fastboot flash recovery) the cm-13.0-20160810-NIGHTLY-condor-recovery.img (instead of TWRP 2.8.7) ? :
CyanogenMod Recovery:
https://download.cyanogenmod.org/get/jenkins/173585/cm-13.0-20160810-NIGHTLY-condor-recovery.img
And then the:
CyanogenMod Build
cm-13.0-20160810-NIGHTLY-condor.zip (322.76 MB)
https://download.cyanogenmod.org/get/jenkins/173585/cm-13.0-20160810-NIGHTLY-condor.zip
And Finally - Flash gapps 6.0:
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
https://www.androidfilehost.com/?fid=24533103863139560
One last question, since I know that the CM13 is not based in an official Motorola release, I would like to know what is working flawlessly, and what is not working with in the Moto-E if I use this CM13 ROM ?
Please excuse all the questions, but I will like to be fully sure of the method and the correct files, that I have to use to successfully flash my Moto-E to CM13, to avoid future problems.
Thanks again for all your help !!
@ulises.rodriguez
I would recommend following steps
1)Download latest twrp (3.0.2) from twrp official website
2) Reboot into recovery and choose downloaded recovery image and then select recovery partition
(Twrp updated .. u can reboot for file transfer)
3)Transfer rom and gapps6.0 to sd card
4)Reboot into twrp and wipe /system,/data,/cache,/dalvikcache partitions (internal storage is optional )
5)choose rom zip (latest from cm downloads)
6)after rom zip is flashed successfully .. choose gapps zip (use open gapps Pico)
7)After successfully flashing both files .. reboot into system and enjoy new rom on moto e
Cm13 today's nightly working flawless for me
(And regarding your first sentence of post(1000 thanks ) .. I can't see them on my profile XD (Just joking .. hit thanks only if u want ))
Ignore any English grammatical mistakes in the post
ABSathe said:
@ulises.rodriguez
I would recommend following steps
1)Download latest twrp (3.0.2) from twrp official website
2) Reboot into recovery and choose downloaded recovery image and then select recovery partition
(Twrp updated .. u can reboot for file transfer)
3)Transfer rom and gapps6.0 to sd card
4)Reboot into twrp and wipe /system,/data,/cache,/dalvikcache partitions (internal storage is optional )
5)choose rom zip (latest from cm downloads)
6)after rom zip is flashed successfully .. choose gapps zip (use open gapps Pico)
7)After successfully flashing both files .. reboot into system and enjoy new rom on moto e
Cm13 today's nightly working flawless for me
(And regarding your first sentence of post(1000 thanks ) .. I can't see them on my profile XD (Just joking .. hit thanks only if u want ))
Ignore any English grammatical mistakes in the post
Click to expand...
Click to collapse
ABSathe, thanks again for your fast response and also valuable help !
Is this the open gapps6.0 Pico that you have installed in your Moto-E ? :
open_gapps-arm-6.0-pico-20160810.zip
http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico
With regard to my question about how well it is currently working the CM13 in the Moto-E, and what is not working yet...
I was asking because I've heard that as the CM13 was not based on a official version of Motorola, some features of the Moto-E did not work very well...
So, I would like to know, if the proximity sensor, Phone Signal Bluetooth, Camera, Gyroscope and all other sensors, if all of them are working well, or if any have some limitations ?
Are there any features that you have found that work best with the CM13, than with the official ROMs from Motorola for the Moto-E ?
Thanks again for helping me and always answer all my requests !
ulises.rodriguez said:
ABSathe, thanks again for your fast response and also valuable help !
Is this the open gapps6.0 Pico that you have installed in your Moto-E ? :
open_gapps-arm-6.0-pico-20160810.zip
http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico
With regard to my question about how well it is currently working the CM13 in the Moto-E, and what is not working yet...
I was asking because I've heard that as the CM13 was not based on a official version of Motorola, some features of the Moto-E did not work very well...
So, I would like to know, if the proximity sensor, Phone Signal Bluetooth, Camera, Gyroscope and all other sensors, if all of them are working well, or if any have some limitations ?
Are there any features that you have found that work best with the CM13, than with the official ROMs from Motorola for the Moto-E ?
Thanks again for helping me and always answer all my requests !
Click to expand...
Click to collapse
All the sensors are working perfectly
And regarding gapps .. I have installed older package (which I downloaded in July) .. but the latest one will just work fine
And latest nightly of cm13 is working perfectly for me.. so go for it
Sent from my Nexus 5X using XDA Labs
Help... i want to change my installed rom pixel experience 10... So can I shift 1 custom rom to other custom rom by using twrp (PE android 10 to miui 11 ) or flash stock and then flash custom rom??
.... Scare of brick device ...
A$h!$h said:
Help... i want to change my installed rom pixel experience 10... So can I shift 1 custom rom to other custom rom by using twrp (PE android 10 to miui 11 ) or flash stock and then flash custom rom??
.... Scare of brick device ...
Click to expand...
Click to collapse
You can change from one custom rom to another without falling back to the stock rom via TWRP.