Related
I purchased outright this Moto E 4G LTE from Staples.
It's not locked to any single carrier and I more than likely will use it as a pocket computer, rather than a talk and text phone.
The details from within the phone are as follows:
Model Number - Moto E (2nd Generation) with 4G LTE
Hardware SKU - XT1527
Android Version - 5.0.2
Baseband version - M8916_200608.08.02.58.15R SURNIA_RETCA_CUST
Kernel version - 3.10.49-gb86829a [email protected] #1 Tue Aug 4 14:44:21 CDT 2015
System version - 22.46.8.surnia_retca.retca.en.CA retca
Build number - LXI22.50-53.8
This is my first plunge into the world of unlocking, rooting, and flashing Android OS.
So far I've been able to gather that cybojenix and squid2 have highly regarded threads and downloads related to the Moto E 4G LTE but the high volume of custom roms, TWRP files, modem files, gapps, patches to fix issues with the camera and patches to eliminate a warning message that warns of a rooted bootloader, etc have left me somewhat overwhelmed lost. I am in need of a short list of what I absolutely need to do what I want to do, and some hints of what extras would work best with my phone in terms of custom roms or whatever relevant.
I'd like to root my phone so that I can run a specific app not related to xdadevelopers. My needs are mostly related to security and anonymity because in my professional life I conduct social research with vulnerable populations and the ethics of my profession dictate a strict code of conduct in this vein.
[As an aside --The app I use unobtrusively requests root access and I fully trust the app since I am very familiar with its history and development to date. The app is found found at f-droid if anyone is interested in checking out f-droid's offerings.]
My questions are these:
What version of twrp-surnia-3.0.0-r*.img will my Moto E work with?
Motorola says my Android Version 5.0.2 is fully up to date when I try to use the in-phone System Updates feature from the About Phone tab in Settings. However I've read in XDAdevelopers that this version of Android can run into problems when using a later version of TWRP.
Can I install a flavour of CM13 straight from Android Version 5.0.2 or do I need to somehow install an Android Version of 5.1 as a first step?
What flavour of CM (Custom ROM) works best with this phone?
I recognize this thread is a bit long winded but I hope to have provided all the necessary details required to seek help from the many expert coders, programmers, and operators dedicated to xda-developers.
Thank you for taking time to read this, and many more thanks if you happen to contribute to any of the solutions that might follow.
Have a wonderful evening.
lostcelt said:
I purchased outright this Moto E 4G LTE from Staples.
It's not locked to any single carrier and I more than likely will use it as a pocket computer, rather than a talk and text phone.
The details from within the phone are as follows:
Model Number - Moto E (2nd Generation) with 4G LTE
Hardware SKU - XT1527
Android Version - 5.0.2
Baseband version - M8916_200608.08.02.58.15R SURNIA_RETCA_CUST
Kernel version - 3.10.49-gb86829a hud[email protected] #1 Tue Aug 4 14:44:21 CDT 2015
System version - 22.46.8.surnia_retca.retca.en.CA retca
Build number - LXI22.50-53.8
This is my first plunge into the world of unlocking, rooting, and flashing Android OS.
So far I've been able to gather that cybojenix and squid2 have highly regarded threads and downloads related to the Moto E 4G LTE but the high volume of custom roms, TWRP files, modem files, gapps, patches to fix issues with the camera and patches to eliminate a warning message that warns of a rooted bootloader, etc have left me somewhat overwhelmed lost. I am in need of a short list of what I absolutely need to do what I want to do, and some hints of what extras would work best with my phone in terms of custom roms or whatever relevant.
I'd like to root my phone so that I can run a specific app not related to xdadevelopers. My needs are mostly related to security and anonymity because in my professional life I conduct social research with vulnerable populations and the ethics of my profession dictate a strict code of conduct in this vein.
[As an aside --The app I use unobtrusively requests root access and I fully trust the app since I am very familiar with its history and development to date. The app is found found at f-droid if anyone is interested in checking out f-droid's offerings.]
My questions are these:
What version of twrp-surnia-3.0.0-r*.img will my Moto E work with?
Motorola says my Android Version 5.0.2 is fully up to date when I try to use the in-phone System Updates feature from the About Phone tab in Settings. However I've read in XDAdevelopers that this version of Android can run into problems when using a later version of TWRP.
Can I install a flavour of CM13 straight from Android Version 5.0.2 or do I need to somehow install an Android Version of 5.1 as a first step?
What flavour of CM (Custom ROM) works best with this phone?
I recognize this thread is a bit long winded but I hope to have provided all the necessary details required to seek help from the many expert coders, programmers, and operators dedicated to xda-developers.
Thank you for taking time to read this, and many more thanks if you happen to contribute to any of the solutions that might follow.
Have a wonderful evening.
Click to expand...
Click to collapse
The basic steps you need to follow are:
Unlock your bootloader
Flash the XT1527 RETUS 5.1 modem (see http://forum.xda-developers.com/moto-e-2015/help/moto-e-2015-modems-t3296044)
Flash the latest TWRP (my 3.0.1-r1 build as of this moment, see http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649)
From TWRP, go into advanced wipe and erase system, data, cache, and dalvik
Flash CM13 + gapps together in TWRP
Apart from the modem, you don't have to upgrade anything else.
I choose to avoid Cm after reading up on it.
I prefer to use the Stock ROM etc
BUT!
I Root it with SuperSU then make my own Bootlogo + Animation
Then i use Squid's Kernel + Squid's TWRP and No-frills CPU Control (to use some of the options Squid's kernel has)
I believe my setup is cleaner and has more stable support and easier to do learn etc.
I checked on what features CM offers and none of it sound like anything i wanted.
I also don't want to have to fiddle around with Gapps or whatever.
I also seen some drawbacks before with some features on the stock Rom that do not work on CM.
I think most people use it simply because it's popular.
Evaluate your options and choose what is right for you.
First thing you want to do is check if you can unlock your bootloader.
Since your from Canada i bet you can.. i did on mine.
Squid's stuff plus Stock Android is good.. in my opinion better than CM.
squid2 said:
The basic steps you need to follow are:
Unlock your bootloader
Flash the XT1527 RETUS 5.1 modem (see http://forum.xda-developers.com/moto-e-2015/help/moto-e-2015-modems-t3296044)
Flash the latest TWRP (my 3.0.1-r1 build as of this moment, see http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649)
From TWRP, go into advanced wipe and erase system, data, cache, and dalvik
Flash CM13 + gapps together in TWRP
Apart from the modem, you don't have to upgrade anything else.
Click to expand...
Click to collapse
Thank you for responding to my questions, squid2. I am very much honored to have had you taken the time to write on my behalf, this is certainly something to which I feel very privledged.
For the sake of clarity and accuracy I will quickly repeat the steps I just took after reading your answer to this thread. If you do not write into this thread a second time I will assume the steps I just took are indeed the correct ones.
1. I went to http://forum.xda-developers.com/moto...odems-t3296044 as you directed and downloaded only the one folder titled Modem, ignoring the larger file that includes another three folders in addition to the Modem folder (the larger file containing all the four files is 25.79GB, whereas the single Modem folder is just 561MB).
2. I then unzipped the Modem folder and selected the SURNIA-RETUS_5.1.zip, ignoring the SURNIA-RETUS_5.1_new.zip which is also in the Modem folder. (The newer SURNIA-RETUS_5.1_new.zip file is two days newer than the other SURNIA-RETUS_5.1.zip file, but since they are both in the same Modem folder I am taking that to mean I should follow your original instructions precisely as directed. Both files are about the same size, except that the newer file is slightly smaller than the other.)
Again, thank you. Your instructions were vital in enabling me to move forward on this task. We need a bitcoin tip jar for people who take time to help others.
xpmule said:
I choose to avoid Cm after reading up on it.
I prefer to use the Stock ROM etc
BUT!
I Root it with SuperSU then make my own Bootlogo + Animation
Then i use Squid's Kernel + Squid's TWRP and No-frills CPU Control (to use some of the options Squid's kernel has)
I believe my setup is cleaner and has more stable support and easier to do learn etc.
I checked on what features CM offers and none of it sound like anything i wanted.
I also don't want to have to fiddle around with Gapps or whatever.
I also seen some drawbacks before with some features on the stock Rom that do not work on CM.
I think most people use it simply because it's popular.
Evaluate your options and choose what is right for you.
First thing you want to do is check if you can unlock your bootloader.
Since your from Canada i bet you can.. i did on mine.
Squid's stuff plus Stock Android is good.. in my opinion better than CM.
Click to expand...
Click to collapse
Thank you, xpmule. I had been wondering whether it was a good idea to install CM or to use a stock Rom. From what I've been reading the Moto E version of Android is fairly bloat-free and since I really only need a rooted phone there is no real need for CM.
I've learned more than once that messing around with unfamiliar OS can be a recipe for disaster after foolishly timing updates of a Linux or BSD OS when I have papers due or exams to study for.
I'll take some more time to research the other options you recommended and then follow your lead with respect to this phone.
Again I'd like to thank both squid2 and yourself for helping me on this, and may I suggest that people who provide meaningful assistance such as this put a bitcoin wallet addres in their signature so that people like me can show our gratitude .
I Support Bitcoin and i think i said that to Squid before too LOL
But i have before refused some for helping people more than once.
My help is not as much as Squid's though.. he puts in effort for his public projects LOL
I don't think you will see him giving advice too much either.. at least i haven't.
So Squid.. GET a Bitcoin address man
OP good luck.. i think Moto's Android is fairly bloat free.. The stuff Moto put on there is good.
Like the twist the phone to activate the camera app or the app that tweaks the notifications.
I am happy myself just modding the stock firmware.
Thank you squid2, I followed your directions exactly as prescribed and I am now rocking the lastest nightly build of CM on my Moto E. It was fairly easy and I can confirm that everything works just fine.
And thank you as well, xpmule. I was going to follow your instructions too but when I got to a certain point in my process and my phone asked if I was sure I wanted to reboot even though there was no OS installed, well I had one of those moments.
Thank you, thank you, THANK YOU!!
Now it's time to explore this CM OS and see what all the fanfare is really about. )
Redmi note 3 ROM Uploaders please read!
I have been flashing stock roms for a few years now and I have noticed with this device that many of the uploaders are not providing all the details just some of the following:
Detailed description
Is bootloader to be unlocked first
Is a custom recovery needed
Full instructions on how to install
Screenshots
bug list
Which Gapps package to use
Please provide all (the above) the neccessary information so we can make the decision is this ROM good for us to flash on our phones.
There needs to be a template for ROM postings so it can be easy for the end users. (Forum moderators will know the formula so I ask ye guys to sticky a template)
Thank you (ordered mine 3 days ago come on gearbest I wants my precioussss)
rslatara said:
Redmi note 3 ROM Uploaders please read!
I have been flashing stock roms for a few years now and I have noticed with this device that many of the uploaders are not providing all the details just some of the following:
Detailed description
Is bootloader to be unlocked first
Is a custom recovery needed
Full instructions on how to install
Screenshots
bug list
Which Gapps package to use
Please provide all (the above) the neccessary information so we can make the decision is this ROM good for us to flash on our phones.
There needs to be a template for ROM postings so it can be easy for the end users. (Forum moderators will know the formula so I ask ye guys to sticky a template)
Thank you (ordered mine 3 days ago come on gearbest I wants my precioussss)
Click to expand...
Click to collapse
First thing, its not stock rom, its custom rom.
Second, the developers are not being paid, and thus whatever thay are doing, just accept it and ask for help, not post post like this to command them to list things that are obviously common sense.
1. CM13 Nightly, this 2 words give enough description, what more do you need. In this time, if you don't know what cm13 is then don't buy an android. Nightly means that there are still bugs, both minor and major, and sometimes it means that there are some things broken too. The devs also list whats working or whats not. They can't list every single thing.
2. You are flashing custom rom, thus you must have custom recovery like twrp, in order to install it you must first unlock your bootloader. If you have custom recovery, then it doesn't matter whether your bootloader is unlocked or not.
3. Did you really just asked if custom recovery is needed, are you a fool or what. Let me make this clear, if you want to flash a rom, how are you supports to so without a custom recovery. Stock recovery can't flash rom, neither it can make backup, restore backup and lots of things. The most basic thing to do even before rooting is to flash a custom recovery. Without custom recovery you can't even properly root. Well you can root with some apps, but custom recovery makes it easier, just download supersu and flash it with recovery.
4. Whats there to know. If you have custom recovery, then first create a backup. Almost every thread that i have ever read on xda, it is stated every where to always make a backup before doing anything, even rooting. Then, wipe data cache dalvik system, and then flash the zip file. After that if you wish flash the gapps.
5. What do you need screenshot for. Haven't you ever saw CM13 or ressurection remix. Just google it. they are not obliged to post it here for your convenience.
6. They do provide bugs, whats working or what not. And its not like they know a bug and haven't told other about it. They, in most cases don't know how many bugs there are, the other users tell them the bugs and they fix it.
7. Why would they tell you which gapps package to use. Do they work for google. Anyway, just google gapps, your rom version, ie cm12 or cm13, you mob architecture, arm64 or arm32 or whatever, and just download it. There is no geek stuff behind it that you can't do it yourself.
And finally, you are not paying them do anything, they are doing this because they like doing this. They are not even getting paid by this. So you ordering them to these things which you can do yourself after some googling and using your brain a bit, is just unjust. Just accept what they are doing, thank them, enjoy the rom, and report the bugs, etc etc, and have fun.
archit.bajpai.ab said:
First thing, its not stock rom, its custom rom.
Second, the developers are not being paid, and thus whatever thay are doing, just accept it and ask for help, not post post like this to command them to list things that are obviously common sense.
1. CM13 Nightly, this 2 words give enough description, what more do you need. In this time, if you don't know what cm13 is then don't buy an android. Nightly means that there are still bugs, both minor and major, and sometimes it means that there are some things broken too. The devs also list whats working or whats not. They can't list every single thing.
2. You are flashing custom rom, thus you must have custom recovery like twrp, in order to install it you must first unlock your bootloader. If you have custom recovery, then it doesn't matter whether your bootloader is unlocked or not.
3. Did you really just asked if custom recovery is needed, are you a fool or what. Let me make this clear, if you want to flash a rom, how are you supports to so without a custom recovery. Stock recovery can't flash rom, neither it can make backup, restore backup and lots of things. The most basic thing to do even before rooting is to flash a custom recovery. Without custom recovery you can't even properly root. Well you can root with some apps, but custom recovery makes it easier, just download supersu and flash it with recovery.
4. Whats there to know. If you have custom recovery, then first create a backup. Almost every thread that i have ever read on xda, it is stated every where to always make a backup before doing anything, even rooting. Then, wipe data cache dalvik system, and then flash the zip file. After that if you wish flash the gapps.
5. What do you need screenshot for. Haven't you ever saw CM13 or ressurection remix. Just google it. they are not obliged to post it here for your convenience.
6. They do provide bugs, whats working or what not. And its not like they know a bug and haven't told other about it. They, in most cases don't know how many bugs there are, the other users tell them the bugs and they fix it.
7. Why would they tell you which gapps package to use. Do they work for google. Anyway, just google gapps, your rom version, ie cm12 or cm13, you mob architecture, arm64 or arm32 or whatever, and just download it. There is no geek stuff behind it that you can't do it yourself.
And finally, you are not paying them do anything, they are doing this because they like doing this. They are not even getting paid by this. So you ordering them to these things which you can do yourself after some googling and using your brain a bit, is just unjust. Just accept what they are doing, thank them, enjoy the rom, and report the bugs, etc etc, and have fun.
Click to expand...
Click to collapse
1. I know what CM is this is about description not quick copy and pastes from another website.
2. Some modified roms can be ran from the stock recovery.
3. You are a fool this is information for the end user I will slap you with a fresh wet fish!
4. Information is key.
5. Screenshots show people what they are flashing very helpful to the end user
6. They don't always bub!
7. Again inofrmation helps to clarify lot's of things.
Not all the guys that post are the actual devs THAT DO IT RIGHT, some are just bad copy paste jobs coz they wanna be cool n **** and don't Fu(&ing tell me not use andorid you little pretend dev snot! :victory:
rslatara said:
1. I know what CM is this is about description not quick copy and pastes from another website.
2. Some modified roms can be ran from the stock recovery.
3. You are a fool this is information for the end user I will slap you with a fresh wet fish!
4. Information is key.
5. Screenshots show people what they are flashing very helpful to the end user
6. They don't always bub!
7. Again inofrmation helps to clarify lot's of things.
Not all the guys that post are the actual devs THAT DO IT RIGHT, some are just bad copy paste jobs coz they wanna be cool n **** and don't Fu(&ing tell me not use andorid you little pretend dev snot! :victory:
Click to expand...
Click to collapse
If you are using a 32bit windows, then do you ask others which application to install, 32bit or 64bit. Man you are a joke, it's not information, its common sense. information is which partition is used for what purpose. How to restore imei. How to unlock lte band, not which gapps to flash. And there is no stock recovery out ther which flash custom roms. The only roms you can flash with stock recovery are ota.
archit.bajpai.ab said:
If you are using a 32bit windows, then do you ask others which application to install, 32bit or 64bit. Man you are a joke, it's not information, its common sense. information is which partition is used for what purpose. How to restore imei. How to unlock lte band, not which gapps to flash. And there is no stock recovery out ther which flash custom roms. The only roms you can flash with stock recovery are ota.
Click to expand...
Click to collapse
Hey I am just a certified IT Technician working for the IT department of a mutlinational company what would I know and I spit on x86 always have..even my windows vista was x64 boi!!!!
rslatara said:
Hey I am just a certified IT Technician working for the IT department of a mutlinational company what would I know and I spit on x86 always have..even my windows vista was x64 boi!!!!
Click to expand...
Click to collapse
So if you are not a noob then why are u asking for such things that are common sense. Nobody ask these things now. I just passed class 12 and i know most of the procedure for tweaking an android. I can even write partition table. You just have to search. Not post like this and expect the dev to post them too. Do a little bit more work to achieve something.
archit.bajpai.ab said:
So if you are not a noob then why are u asking for such things that are common sense. Nobody ask these things now. I just passed class 12 and i know most of the procedure for tweaking an android. I can even write partition table. You just have to search. Not post like this and expect the dev to post them too. Do a little bit more work to achieve something.
Click to expand...
Click to collapse
Coming from a Huawei g510 where i got my roms on Modaco, and The zenfone 2 here at xda the posts were well put togther with all the info needed , I have found quiet a few here with very little and it's kinda lazy on the posters part.
That is all. I ain't a programmer (although i touched on some c++) but I ain't a noob just like details and not everyone is well informed and there a newbies to flashing roms it's to help them too not brick a device.
archit.bajpai.ab said:
So if you are not a noob then why are u asking for such things that are common sense. Nobody ask these things now. I just passed class 12 and i know most of the procedure for tweaking an android. I can even write partition table. You just have to search. Not post like this and expect the dev to post them too. Do a little bit more work to achieve something.
Click to expand...
Click to collapse
Coming from a Huawei g510 where i got my roms on Modaco, and The zenfone 2 here at xda the posts were well put togther with all the info needed , I have found quiet a few here with very little info and it's kinda lazy on the posters part.
I ain't a programmer (although i touched on some c++) but I ain't a noob, I just like details and not everyone is well informed and there a newbies to flashing roms it's to help them to not brick a device.
From what I see it's mostly non devs just copy paste guys who are doing it.
Does it hurt to have a small guide or at least the fundemntals of requrements for the installation of each rom?
Waiting on my redmi still order prcessing, hurry gearbest hurry I am back on my g510 as my asus went for a swim in my tiolet!
rslatara said:
Coming from a Huawei g510 where i got my roms on Modaco, and The zenfone 2 here at xda the posts were well put togther with all the info needed , I have found quiet a few here with very little and it's kinda lazy on the posters part.
That is all. I ain't a programmer (although i touched on some c++) but I ain't a noob just like details and not everyone is well informed and there a newbies to flashing roms it's to help them too not brick a device.
Click to expand...
Click to collapse
Nice idea, looks like there's no room for a newbie on XDA anumore (in remembrance of XDA 2012).
Sent from my Redmi Note 3 using XDA Labs
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
tdssmarty16 said:
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
Click to expand...
Click to collapse
Bootloader: Go with the official way. The tool can be used again and again as long as you got the permission. There are many cases of bootloop and bricked phones when using unofficial method. Just goto miui unlock page and login with you id, you will get unlock permission within a week.
Download miunlock tool and follow the onscreen instructions.
Twrp: use the official version or if you want f2fs (which is not that big of a deal) thestrixs twrp. I prefer the official one. Reasons: no idea. The cofface version is for those who want twrp to remain unchanged even when they are using miui rom. If you plan to port to cm or anyother rom no need for cofface. The alka version lets you backup every single partition and allow you restore them seperately. No need to use this as you can always use miflash to flasb miui rom again. The only backup you will ever need is efs which can be done with any version.
I prefer a partition dump instead of twrp backup. If you want to know how to create a fool proof backup of efs see my guide. Just search it under discussions and you will find it.
Boot image:
There is no need. The custom cooked boot image is only eequired if you use miui and want to keep stock recovery from replacing twrp. Again why do all this when you can flash twrp again.
Any other stuff:
You can check out guides for installing rom, xposed, i dont know.
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
tdssmarty16 said:
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
Click to expand...
Click to collapse
Bootloader: Go with the official way. The tool can be used again and again as long as you got the permission. There are many cases of bootloop and bricked phones when using unofficial method. Just goto miui unlock page and login with you id, you will get unlock permission within a week.
Download miunlock tool and follow the onscreen instructions.
Twrp: use the official version or if you want f2fs (which is not that big of a deal) thestrixs twrp. I prefer the official one. Reasons: no idea. The cofface version is for those who want twrp to remain unchanged even when they are using miui rom. If you plan to port to cm or anyother rom no need for cofface. The alka version lets you backup every single partition and allow you restore them seperately. No need to use this as you can always use miflash to flasb miui rom again. The only backup you will ever need is efs which can be done with any version.
I prefer a partition dump instead of twrp backup. If you want to know how to create a fool proof backup of efs see my guide. Just search it under discussions and you will find it.
Boot image:
There is no need. The custom cooked boot image is only eequired if you use miui and want to keep stock recovery from replacing twrp. Again why do all this when you can flash twrp again.
Any other stuff:
You can check out guides for installing rom, xposed, i dont know.
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
tdssmarty16 said:
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
Click to expand...
Click to collapse
Bootloader: Go with the official way. The tool can be used again and again as long as you got the permission. There are many cases of bootloop and bricked phones when using unofficial method. Just goto miui unlock page and login with you id, you will get unlock permission within a week.
Download miunlock tool and follow the onscreen instructions.
Twrp: use the official version or if you want f2fs (which is not that big of a deal) thestrixs twrp. I prefer the official one. Reasons: no idea. The cofface version is for those who want twrp to remain unchanged even when they are using miui rom. If you plan to port to cm or anyother rom no need for cofface. The alka version lets you backup every single partition and allow you restore them seperately. No need to use this as you can always use miflash to flasb miui rom again. The only backup you will ever need is efs which can be done with any version.
I prefer a partition dump instead of twrp backup. If you want to know how to create a fool proof backup of efs see my guide. Just search it under discussions and you will find it.
Boot image:
There is no need. The custom cooked boot image is only eequired if you use miui and want to keep stock recovery from replacing twrp. Again why do all this when you can flash twrp again.
Any other stuff:
You can check out guides for installing rom, xposed, i dont know.
thanx a lot helping out mahn
will go with the official unlock
and official twrp
i have been waiting a lot to try cm 13
Hi All!
Is there a way to get lineage 14.x on le pro 3 Elite (X722)? I've been searching online, but all information seems to be related to X720 model, and there is basically nothing (or very little) regarding the X722... I was hoping to be able to root my device, Install lineage OS, and then un-root (due to using some corporate apps which don't allow devices to be rooted).
Please let me know in case you have some info. I will greatly appreciate your help!
Thanks!
Mick
Hey
As far as i know Leeco didn't released their open source code for x722 and that's why there is no custom roms. I'm a little bit confused because they shared their open source code for many models and i don't know why they didn't do that for x722 :C
tried booting this rom
Otojestemja said:
Hey
As far as i know Leeco didn't released their open source code for x722 and that's why there is no custom roms. I'm a little bit confused because they shared their open source code for many models and i don't know why they didn't do that for x722 :C
Click to expand...
Click to collapse
I want to know did u tried this rom because the specs are similar except for nfc and slow processor on chinese version sd820 instead of sd821
Ab20000 said:
I want to know did u tried this rom because the specs are similar except for nfc and slow processor on chinese version sd820 instead of sd821
Click to expand...
Click to collapse
I didn't tried any rom and at the moment i don't have this phone. I think different processor than in leeco x720/x727 make it useless to use the 720/727 rom for this device and can only lead to brick phone.
So why does TWRP for x720/x727 work flawlessly on x722?
Also lineage OS developer for lepro3 asked if anyone can give him log files from lineage boot on x722 then he can probably make it work. It seems the issue is not CPU (i guess it is same linux kernel and drivers anyway), but somehow changed boot sequence of the x722 then x720/x727, but i don't really understand this stuff.
evlo said:
So why does TWRP for x720/x727 work flawlessly on x722?
Also lineage OS developer for lepro3 asked if anyone can give him log files from lineage boot on x722 then he can probably make it work. It seems the issue is not CPU (i guess it is same linux kernel and drivers anyway), but somehow changed boot sequence of the x722 then x720/x727, but i don't really understand this stuff.
Click to expand...
Click to collapse
thats why I dislike this company. They have placed very small batteries in their phones and removed headphone jacks and no sdcard slot. Plus they are not releasing sources of these China specific models.
evlo said:
So why does TWRP for x720/x727 work flawlessly on x722?
Also lineage OS developer for lepro3 asked if anyone can give him log files from lineage boot on x722 then he can probably make it work. It seems the issue is not CPU (i guess it is same linux kernel and drivers anyway), but somehow changed boot sequence of the x722 then x720/x727, but i don't really understand this stuff.
Click to expand...
Click to collapse
huh, if he can guide me I will provide him with the logs that he needs. It would make this phone sooooooo much better if we could put lineage os on it.
Ab20000 said:
thats why I dislike this company. They have placed very small batteries in their phones and removed headphone jacks and no sdcard slot. Plus they are not releasing sources of these China specific models.
Click to expand...
Click to collapse
I don't agree regarding the battery, but an sd slot I definitely miss... the phone itself is good, but it really sucks that we can't put lineage on it. I wish I did proper research before buying it, as I would probably go for a different one.
mick_novi said:
I don't agree regarding the battery, but an sd slot I definitely miss... the phone itself is good, but it really sucks that we can't put lineage on it. I wish I did proper research before buying it, as I would probably go for a different one.
Click to expand...
Click to collapse
yea you are right . I saw x626 with 4/64gb on gearbeast for less than 140. But I cancelled the order because there is no ROM support. This model was not released outside of China so it has no google play store originally and no MTK model was made for market outside CN like the 1s thus flashing Indian/Russian or other international ROM is not a possibility.
did anyone update a lineage ROM on the Le Pro x722?
Ab20000 said:
yea you are right . I saw x626 with 4/64gb on gearbeast for less than 140. But I cancelled the order because there is no ROM support. This model was not released outside of China so it has no google play store originally and no MTK model was made for market outside CN like the 1s thus flashing Indian/Russian or other international ROM is not a possibility.
Click to expand...
Click to collapse
could anyone try and test the lineage at this page download.lineageos.org/zl1 and try it with the x722 and check if it all works good? or do you have any similar hint?
diegosum said:
could anyone try and test the lineage at this page download.lineageos.org/zl1 and try it with the x722 and check if it all works good? or do you have any similar hint?
Click to expand...
Click to collapse
The problem is that the bootloader is locked and there is currently no root for the device... and as it seems like there will never be. one...
It would make this phone so much better if we had the chance to put lineage on it, as LeEco is going under (if not already), and there will be no future updates to the software, even though there are so many bugs... such as you can't change default browser, expand notifications, and so on....
mick_novi said:
The problem is that the bootloader is locked and there is currently no root for the device... and as it seems like there will never be. one...
It would make this phone so much better if we had the chance to put lineage on it, as LeEco is going under (if not already), and there will be no future updates to the software, even though there are so many bugs... such as you can't change default browser, expand notifications, and so on....
Click to expand...
Click to collapse
yes, and the camera not auto-focusing when changing from a far to a closer focus or the contrary and you have to be tapping on the screen every time
so in the end maybe the lineage 14 for the x720 and x727 might work fine but the point is that the x722 has a locked door about bootloader and can't open and enter to work on it?
diegosum said:
yes, and the camera not auto-focusing when changing from a far to a closer focus or the contrary and you have to be tapping on the screen every time
so in the end maybe the lineage 14 for the x720 and x727 might work fine but the point is that the x722 has a locked door about bootloader and can't open and enter to work on it?
Click to expand...
Click to collapse
Yes, exactly. This lineage for x720 might work, but currently there is no way to install it.... I really hope that sometime in the future, installing lineage will be possible, that someone figures it out (fingers crossed it happens sometime soon)
diegosum said:
could anyone try and test the lineage at this page download.lineageos.org/zl1 and try it with the x722 and check if it all works good? or do you have any similar hint?
Click to expand...
Click to collapse
If you have American single sim model then you have to unlock bootloader first then try. I heard most roms are compatible but I am not sure about NFC status.
Hi guys, can you provide any working TWRP and guide how to root my X722?
Thanks
mick_novi said:
huh, if he can guide me I will provide him with the logs that he needs. It would make this phone sooooooo much better if we could put lineage os on it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=73318157&postcount=760
https://forum.xda-developers.com/showpost.php?p=73323157&postcount=762
I will also be able to help once my phone arrives. Wondering what firmware i'll get it with (from BangGood).
When I scanned xda I saw official lineage for x72x so i assumed it was supported - the title is a bit misleading. Probably wouldn't have ordered it if I read the whole thread.
That said, I'm in it for the long haul now, and might actually be a good opportunity for me to actually give something back to the xda community (besides $).
Too many wrong infos in this topic.
- Bootloader is locked ONLY in 026s stock rom and it CAN be unlocked by flashing 001d dev release.
- You DON'T flash x720 roms to x722 since you will easily get a nice brick.
- You DON'T flash stock 026s through TWRP (especially from geekbuying vendor 020s rom with twrp)
- x722 has root in tora33 custom rom - this is a fresh stuff so check that thoroughly
dakok said:
Too many wrong infos in this topic.
- Bootloader is locked ONLY in 026s stock rom and it CAN be unlocked by flashing 001d dev release.
- You DON'T flash x720 roms to x722 since you will easily get a nice brick.
- You DON'T flash stock 026s through TWRP (especially from geekbuying vendor 020s rom with twrp)
- x722 has root in tora33 custom rom - this is a fresh stuff so check that thoroughly
Click to expand...
Click to collapse
I used the tora33 no root custom in x722, but the fingerprint sensor stoped, so i put the Dev ROM again
dakok said:
- x722 has root in tora33 custom rom - this is a fresh stuff so check that thoroughly
Click to expand...
Click to collapse
Do you have a link for this ROM?
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Well, I have the same phone. Couldn't find ROMs for it.
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Click to expand...
Click to collapse
look in this forum here, there are a couple floating around for it, I've made one, that I was able to fully flash to mine and has touch (Android 10. there's another that is 11 on here too by another poster), but as there are multiple display options out there it seems for how they were made, that is the sticking point, as not all will behave properly when booted into a recovery like mode it seems. I have tried installing it over bootloader and it will have touch then, but when flashed to recovery the touch never activates properly. So it all likely comes to that, as we'll need combine them in, properly applying proper checks for each display type and having it use the proper driver files, since can't load them all at once or it breaks things.
Working shrp for Borneo
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
First place to start: twrpdtgen
Read the "readme"
Also check out:
[DEV]How to compile TWRP touch recovery
Device tree made from A10. Should still be relevant for A11.
Kernel for A10. Unfortunately I don't think Moto released the one for A11 yet. You can ask on their GitHub and devs might consider your request.
TWRP for A11. Touch is working.
Edit : here's a link for the device tree (in text) from A11
maybe this will work
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
maybe this will help probably https://github.com/MotorolaMobilityLLC/kernel-msm
UPDATE: I have a telegram account where we are discussing how to make a custom lineage OS. I'm at the gathering stage and in the process of porting a device tree. For starters I want to start with lineage OS 18 because its the same android version the stock OS is, to be on the safe side, and that I've never done ROMS before.
Moto G Power 2021
I now have a device tree with the help of AOSPdtgen from the stock ROM from mirrors.lolinet: https://github.com/thebestofall007/android_device_motorola_borneo
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
thebestofall007 said:
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
Click to expand...
Click to collapse
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
KILLFIREY1389 said:
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
Click to expand...
Click to collapse
The error turned out to be entries in the proprietary-files.text file that needed to be deleted.
@thebestofall007 If you'll suceed. please take in consideration to build \e\ (aka deGoogled Lineage) too.
Here's a couple of interesting links that may help:
https://doc.e.foundation/support-topics/build-e
https://community.e.foundation/t/howto-building-e-roms-a-beginners-guide/26371
Last but not least, we've also suggested them (check here) to setup a "build (V)Machine" by modding this colab notebook to made it device agnostic:
https://github.com/viam1-dev/colab_lineage_build
Hope can "inspire" you.
Thanks in advance.
Does anyone have a complete list of sources so far? I have some experience in the past building ROMs for Android 5 and I wouldn't mind trying. I have a lot of computer resources to dedicate to building as well.
Device tree: https://github.com/thebestofall007/android_device_motorola_borneo-old
Does anyone know if there is a kernel source? I looked on the Moto github and couldn't find one. Is everyone using prebuilt for the time being? Also, do we need a vendor tree?
Thanks