I've built a TWRP recovery for the 2015 Moto E 3G. This model is also known as Styx 3G, and has the codename otus.
3G model only! If you have the LTE model, use my LTE recovery instead.
Downloads are available on the downloads tab. In case you encounter any issues, I've also posted the stock recovery for otus on the downloads tab.
To try it out without flashing, run:
Code:
fastboot boot twrp.img
To flash it:
Code:
fastboot flash recovery twrp.img
Try at your own risk. I expect everything to work, but I make no guarantees.
I would like to thank cybojenix for creating the first-gen Moto E recovery. I used his device tree as a reference when creating mine.
Device Tree: https://github.com/sultanqasim/android_device_motorola_otus/tree/twrp
Kernel: https://github.com/sultanqasim/android_kernel_motorola_otus/tree/twrp
XDA:DevDB Information
TWRP for Moto E 3G (2015), Tool/Utility for the Moto E 2015
Contributors
squid2, cybojenix
Source Code: https://github.com/sultanqasim/android_device_motorola_otus
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-16
Created 2015-04-17
Last Updated 2018-08-16
Reserved
My initial test release is up. Try it at your own risk, I don't know what works and what doesn't. All I know is that it can boot and see the on board storage. Thanks to @Ravx and @Hakkinukai for initial testing. If you want to stay safe, don't flash anything with it until I'm able to confirm that it works properly. I'm still waiting on my test unit to arrive.
For the adventurous, try it out and let me know what works and what doesn't. Be careful though, it's untested and could mess up your device. I'm not responsible for any problems it may cause you.
squid2 said:
My initial test release is up. Try it at your own risk, I don't know what works and what doesn't. All I know is that it can boot and see the on board storage. Thanks to @Ravx and @Hakkinukai for initial testing. If you want to stay safe, don't flash anything with it until I'm able to confirm that it works properly. I'm still waiting on my test unit to arrive.
For the adventurous, try it out and let me know what works and what doesn't. Be careful though, it's untested and could mess up your device. I'm not responsible for any problems it may cause you.
Click to expand...
Click to collapse
Further test results:
1.) Was able to succesfully backup my system with the recovery.
2.) wiping data gave error ( error code 255 i think ) but the data was still gone and the device got factory reset.
3.) Succesfully restored the data from the created backup.
will try to flash SuperSu now.:good::good:
Edit: The device is Successfuly rooted.
Here is the Screenshot of Successful Root.:good::good::good::good:
Bro i have created a saperate Guide for rooting. I hope you dont mind.
Glad to hear that it is mostly working. I'll look into the data wiping error when I get my test device.
Thank you very much squid
i try this command 'fastboot boot twrp-otus-2.8.6-test3.img'
and in first attempt , i got TEAMWIN screen on successful boot MOTO E 2nd Generation.
and from install option ,i install SuperSU from my internal memory.
and my device rooted successfully.
you are :angel:
:victory:
I've posted a new version (2.8.6-test4). This new version solves a problem that prevented my recovery from booting from flash storage. It's also smaller. Thanks to @Hakkinukai for testing.
You can safely flash this recovery to your device by doing
Code:
fastboot flash recovery twrp-otus-2.8.6-test4.img
I make no promises about reliability, but I'd expect most things to work. Use this at your own risk, I'm not responsible for bricking your device. I haven't tested this myself.
To avoid confusion, I've removed the old version (2.8.6-test3) from the downloads tab.
Thank you very much, I could finally rooting my moto E,
#Off topic could please make a version updated for the moto E first generation, the current version is 2.7.1.0 and the latest versions have many bugs,
squid2 said:
I've posted a new version (2.8.6-test4). This new version solves a problem that prevented my recovery from booting from flash storage. It's also smaller. Thanks to @Hakkinukai for testing.
You can safely flash this recovery to your device by doing
Code:
fastboot flash recovery twrp-otus-2.8.6-test4.img
I make no promises about reliability, but I'd expect most things to work. Use this at your own risk, I'm not responsible for bricking your device. I haven't tested this myself.
To avoid confusion, I've removed the old version (2.8.6-test3) from the downloads tab.
Click to expand...
Click to collapse
Thanks bro. I will flash and report back :good::good:
Is flashing the new recovery working for you guys. If yes I will update the rooting thread so that the method becomes more easy.
great work man
Ravx said:
Is flashing the new recovery working for you guys. If yes I will update the rooting thread so that the method becomes more easy.
Click to expand...
Click to collapse
The new recovery is working just fine for me, but i cant boot into recovery mode manually, i have to use a third party app either quick boot or apm+.
other than that everything works good.
raghavarora1997 said:
The new recovery is working just fine for me, but i cant boot into recovery mode manually, i have to use a third party app either quick boot or apm+.
other than that everything works good.
Click to expand...
Click to collapse
By booting manually, I presume you mean selecting it from the bootloader menu with the volume keys. What happens when you try that? I've had others report that it works.
squid2 said:
By booting manually, I presume you mean selecting it from the bootloader menu with the volume keys. What happens when you try that? I've had others report that it works.
Click to expand...
Click to collapse
After selecting recovery from the bootloader black screen comes and nothing happens. I've tried it many times with no success.
Sent from my MotoE2 using XDA Free mobile app
raghavarora1997 said:
After selecting recovery from the bootloader black screen comes and nothing happens. I've tried it many times with no success.
Sent from my MotoE2 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm, so it goes black right away and doesn't show the boot logo or unlocked boot loader warning. Strange.
Are you sure that you flashed it correctly? Is anyone else having this issue?
squid2 said:
Hmm, so it goes black right away and doesn't show the boot logo or unlocked boot loader warning. Strange.
Are you sure that you flashed it correctly? Is anyone else having this issue?
Click to expand...
Click to collapse
Yeah I'm sure I've flashed it correctly.
And yes it goes back right away. Still I will flash or again, just to be sure and then report back.
UPDATE: After flashing again I can boot into recovery manually.
Sent from my MotoE2 using XDA Free mobile app
The utterly incompetent Canada Post decided to lose my Moto E 3G. Their customer service was very unhelpful and just told me to contact the sender, and ask them to start a trace with the USPS. Traces take 3 weeks and often get nowhere. This is the fifth package to me that Canada Post has lost in the past two years. On average, I've found that 1 in 5 packages sent to me via Canada Post get lost. That is quite ridiculous, but they are a taxpayer funded government monopoly with no sense of customer service.
In addition to contacting the sender, as a last resort, I've taped a notice inside my mailbox to ask the mailman/woman if they know what they did to my parcel. God knows if I'll ever get it.
Anyway, enough of a rant for now. I'm furious that they lost a package that I spent $200 on (with taxes, shipping, markup etc.)
Due to you, this tut was possible @ http://androidmtk.com/root-motorola-moto-e-3g-2015
Good news! My Moto E was delivered to the wrong address by Canada Post, but the people who received it brought it to me yesterday. I've started looking into porting CM12.1 to otus, though it will probably be a week or so before I have something to show.
I Find some bugs:
1) The USB-OTG don't work (don't mounts)
2) adb sideload don't work (don't finds device)
3) strong button vibration (the default is 80, but 20 is ideal)
Related
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
htcmusic said:
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
Click to expand...
Click to collapse
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
fix-this! said:
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
Click to expand...
Click to collapse
Guys the device was just launched. Right now I'm working on teaming up with Brinly Taylor so we can develop for this.
Moto e 3g Variant boot.img and recovery.img
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Saumitra Yadav said:
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Click to expand...
Click to collapse
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
squid2 said:
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
Click to expand...
Click to collapse
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Ravx said:
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Click to expand...
Click to collapse
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
EDIT: Don't use this image, it's too big and I've identified other issues.
Ravx said:
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
Click to expand...
Click to collapse
This will be possible only when moto release sources,
squid2 said:
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
Click to expand...
Click to collapse
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
squid2 said:
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
Click to expand...
Click to collapse
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Ravx said:
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Click to expand...
Click to collapse
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
squid2 said:
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
Click to expand...
Click to collapse
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Ravx said:
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Click to expand...
Click to collapse
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
squid2 said:
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
Click to expand...
Click to collapse
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Ravx said:
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Click to expand...
Click to collapse
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
squid2 said:
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Ravx said:
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Click to expand...
Click to collapse
I had someone else try it too, with the same result as you. No big surprise to me, didn't expect it to work. I'll make one with a more conventional 3.4.x kernel when I get time.
Otus TWRP Attempt 3
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
squid2 said:
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
Click to expand...
Click to collapse
Bro you have done it. the recovery booted and i moved a file from one folder to another by using file manager. :good::good::laugh:
EDIT: For now i the recovery's file manager isnt showing "build.prop" and other folders in /system
only the "bin" folder is visible. Is it ok beacaause we havent flashed the recovery or its the other way around.
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
This is my version of TWRP built for the 2016 Moto G Play. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the downloads tab.
XDA:DevDB Information
TWRP for Moto G Play (harpia), Tool/Utility for the Moto G4 Play
Contributors
squid2
Source Code: https://github.com/sultanqasim/android_device_motorola_harpia
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-16
Created 2016-09-03
Last Updated 2018-08-16
Thank you so much for your support. TWRP works perfectly. Although after installing SuperSU, the device doesn't boot. This happened to me on several other devices as well and I don't really understand why it sometimes works and sometimes it doesn't. Any help is appreciated
I even tried the latest beta 2.77 without success.
Rotkaeqpchen said:
Thank you so much for your support. TWRP works perfectly. Although after installing SuperSU, the device doesn't boot. This happened to me on several other devices as well and I don't really understand why it sometimes works and sometimes it doesn't. Any help is appreciated
I even tried the latest beta 2.77 without success.
Click to expand...
Click to collapse
Good to know. Thanks again squid2! Quick question, how is the SOT of this device? A lot better than the Moto G3 I'm right?
Another thing: cam anyone use the aida64 app and find the camera Id (sensors) for the rear?
Rotkaeqpchen said:
Thank you so much for your support. TWRP works perfectly. Although after installing SuperSU, the device doesn't boot. This happened to me on several other devices as well and I don't really understand why it sometimes works and sometimes it doesn't. Any help is appreciated
I even tried the latest beta 2.77 without success.
Click to expand...
Click to collapse
any sucess on root bro ?
i want root moto play
Anyone knows pls suggest me
First, a big thanks to squid2. TWRP works perfectly!
charutl said:
Anyone knows pls suggest me
Click to expand...
Click to collapse
1. Install Twrp
2. Back up your phone, just to be safe.
3. Install Automatic flashable zip fix for supersu! - http://forum.xda-developers.com/g4-play/development/automatic-flashable-zip-fix-supersu-t3464396
4. Install SuperSU: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
Reboot your phone. Worked for me 1st time. The phone may restart several times.
mx597turbo said:
First, a big thanks to squid2. TWRP works perfectly!
1. Install Twrp
2. Back up your phone, just to be safe.
3. Install Automatic flashable zip fix for supersu! - http://forum.xda-developers.com/g4-play/development/automatic-flashable-zip-fix-supersu-t3464396
4. Install SuperSU: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
Reboot your phone. Worked for me 1st time. The phone may restart several times.
Click to expand...
Click to collapse
Thanks for your reply & Is this restart problem temporary or permanent???
charutl said:
Thanks for your reply & Is this restart problem temporary or permanent???
Click to expand...
Click to collapse
After installing supersu, the phone restarted from the warning screen once. After that, the phone booted fine.
Amazon version
Safe to assume this does not work for the Amazon version?
Amirusownsu said:
Safe to assume this does not work for the Amazon version?
Click to expand...
Click to collapse
We can't unlock the bootloader
Will this work for the 1601 bell variant? I would think it should as it is a g4 play non Amazon version. At least o would have root till till custom Roms are available. Hey Squid2, great work so far. Is there a way I could send the code for the radio? Kinda of a noob with that aspect.
Ok so i went ahead and did the steps and we have success! xt1601 moto g play is rooted and ready to roll!
Rotkaeqpchen said:
Thank you so much for your support. TWRP works perfectly. Although after installing SuperSU, the device doesn't boot. This happened to me on several other devices as well and I don't really understand why it sometimes works and sometimes it doesn't. Any help is appreciated
I even tried the latest beta 2.77 without success.
Click to expand...
Click to collapse
I Tried this and it worked for me -
http://www.techjit.com/how-to-root-moto-g4-play/
give it a try.
TWRP and Root working on G play
First of all thanks to squid2 , Thanks to this video... I successfully Installed TWRP and Rooted my G4 Play !
Hello and tried to install the recovery and I get this error: error: can not open'twrp.img 'say I have the bootloader unlocked, please help ,xt1602 moto g4 play
nick more said:
Hello and tried to install the recovery and I get this error: error: can not open'twrp.img 'say I have the bootloader unlocked, please help ,xt1602 moto g4 play
Click to expand...
Click to collapse
Rename file to twrp
It works on dual?
All baloney my bootloader isn't eligible ...
Sent from my XT1609 using XDA Free mobile app
How did you guys unlock the bootloader? I have the xt1607 on us cellular and when I type in the unlock data on moto site it says that it's not eligible. I got the phone from the US cellular store. Any help would be great.
Edit: nevermind I got it to go through.
squid2 said:
I've ported TWRP to the new 2016 Moto G Play. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
To temporarily boot this recovery:
To permanently flash it:
The download is up on the downloads tab.
XDA:DevDB Information
TWRP for Moto G Play (harpia), Tool/Utility for the Moto G4 Play
Contributors
squid2
Source Code:https://github.com/sultanqasim/android_device_motorola_harpia
Version Information
Status: Stable
Current Stable Version: 3.0.2-r4
Stable Release Date: 2016-09-02
Created 2016-09-03
Last Updated 2016-09-02
Click to expand...
Click to collapse
Is this working for xt1607 version? Never mind I got it. Works great squid. Is there a boot logo for this yet?
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.
Team Win Recovery Project​
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* specks of dusk sitting on cursors, cursors that mock you--waiting for cursor
* revenge, thermonuclear war, or you getting fired because the alarms failed
* and you could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications or your own free will.
This is the first official build of TWRP for the Motorola Moto G6 (ALI)!
Notes:
Decryption is finicky: Currently only vold decryption is working. This image must be flashed to properly decrypt. Updates may cause issues with decryption.
If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
If you are unable to unlock your phone after restoring a data backup that had a lock code on it (and TWRP is able to decrypt using default password) you'll need remove the '/data/system/locksettings.db' while in TWRP. After that you should be able to reboot into Android and set a lock code. If you cannot then please use this thread as a guide and try again. Bascially you just delete more, however I was able to boot after just deleting the one file with a pattern set (Maybe random luck, maybe not)
If you have any other issues please let me know and I'll work toward fixing them! AS ALWAYS, IT'S YOUR RESPONSIBILITY IF YOU USE THIS SOFTWARE
Known Issues:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
Flashing zips that require BusyBox will not work with the official version right now. I've built an unofficial version to use until a new official build is triggered.
ALI's Changelog: Post #2
Download: twrp.me Download
Unofficial Download (updated more often): twrp-v3.2.3-unofficial-ali-20181110.img
Simple Installation Method:
1) boot to fastboot
2) fastboot flash recovery <twrp-image-name>.img
Other instructions are available on the Official download page. It's up to you to backup your factory recovery first if you wish to have a backup: Post #3
Thanks to the TWRP team and everyone who has put in effort to make these things possible!
@Jleeblanch - Wonderful advice and guidance
@Dadud - testing
@ Everyone at github
@ XDA and the people who provided TWRP compiling threads
If I've forgotten someone who you think needs mention please let me know!
* This page will continue to be edited as more information comes
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP v3.2.3 [2018-10-20], Tool/Utility for the Moto G6
Contributors
dejello
Source Code: [url]https://github.com/TeamWin/android_device_motorola_ali[/URL]
Version Information
Status: Stable
Current Stable Version: 3.2.3-0
Stable Release Date: 2018-10-20
Current Beta Version: 3.2.3 Unofficial
Beta Release Date: 2018-11-10
Created 2018-10-21
Last Updated 2018-11-10
Changelogs
TWRP Changelog:
v3.2.3 changelog
ALI's Official Changelog:
v3.2.3-0 (Oct 20, 2018)
- N/A, first build!
ALI's Temp. Unofficial Changelog:
v3.2.3 (Oct 31, 2018) (This log will get moved to official when it gets updated with these changes)
- Stop using toybox (Use busybox!)
- Added vendor image mount point
Factory Backup Information
It's up to you to determine if you want/need a factory recovery image backup before flashing:
To boot twrp first (it will fail decryption, don't worry about it) just do the following while replacing <twrp> with the actual file name.
Code:
fastboot boot <twrp>.img
Then to back up your stock/factory recovery while booted in TWRP do the following.
Code:
adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img
First [emoji14]
For real tho, nice work and congrats [emoji41]
Woot Woot! Congrats bro?
Lockscreen after restore
Hello, this method (delete lockscreen) after restore backup works for me to ?
Decryption doesn't work for me. XT1925-6 Ali
giant22000 said:
Decryption doesn't work for me. XT1925-6 Ali
Click to expand...
Click to collapse
I'll need more details if I'm to look into it. I also have an xt1925-6. Any logs? What version software are you running? What kind of lock screen are you using (pin, password, pattern, none, etc)? What happened from booting twrp up to the point of decryption failure? The more information I have the better chance I have at rectifying the issue.
[EDIT] I just did some messing around and came across something I hadn't seen before:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
I have added this to the first post.
Damn thanks !
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
aaleej0 said:
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
Click to expand...
Click to collapse
So I guess I will be the one to say it. I'm giving you one warning about this. It's against forum rules to post on multiple threads with the same subject. I've answered your question on the Ali stock firmware thread also. Please read guides and threads instead of skimming through them because it's been answered multiple times. Next time you do this and post the same thing on multiple threads I will be the one reporting you. Have a good day.
I have added an unofficial build tonight (Oct/31/2018) to fix an issue flashing zips that need busybox (Resurrected Kernel, etc) versus toybox. It also adds a 'vendor image' mount point for use in backups and flashing. Once official gets updated this unofficial build will be removed.
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
ninjakira said:
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
Click to expand...
Click to collapse
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
dejello said:
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
Click to expand...
Click to collapse
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face [emoji23][emoji23]I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Jleeblanch said:
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Click to expand...
Click to collapse
I do have it on dual boot with Ubuntu 18.10 it's Just the the random rebooting is persistent still but yeah I personally use use linux distos over Windows lol. My next paycheck I'm having our local computer store called microcenter help me out with a new laptop at least lol
dejello said:
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
Click to expand...
Click to collapse
I'm not able to send the screenshot of termux so here they are. Recovery is 16 mb