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
Related
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)
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.
Don't forget to hit the thanks button.
http://superstarmobility.weebly.com/
New thread: http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130.
(Above TWRP can be flashed with Flashify from Playstore)
Instructions from video:
With phone powered off, hold POWER and VOLUME DOWN buttons until LG logo shows. Release POWER then quickly press and hold again until factory reset menu comes up. Select YES and you will be booted into recovery instead of a factory reset ; )
Thanks @czarsuperstar!
V2 with the proper cmd line from m1 aka LG K7
Reserved.
This the real deal?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
Of course. You looked at the video?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
I've used it and can confirm, first tested it with fastboot without flashing of course(use adb to get to the bootloader: adb reboot bootloader , then fastboot:fastboot boot "twrp.img file, tested then rebooted into bootloader, then flashed via fastboot:fastboot flash "twrp.img file") instructions are for any random person that come by i know you know how to do all this
concerned xda citizen
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
The first twrp was from a htc phone. This is from lg leon lte. Same manufacturer. I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon twrp is missing the options seen on this one. Don't use it. But I'm working on cm_m1 so continue to use the old one and when your phone can't come on have fun getting in recovery. Make it better.
Recovery log
Make a log.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
Check out the LG L70 it's the same way to get in recovery. This must be your first LG phone.
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Go spam the other thread. Over 200 downloads and no problems but there was problems right away with the first version. For your info download Twrp c50 from the Twrp site examine it and ask why it's incomplete. That's why I linked the video of the Twrp from the site and same problems. Bye and leave me be. Hd2 check it out. Czarsuperstar's HTC HD2 android custom roms. Check it out and leave me alone. Thanks for your concern. Oh and for your info we have the same keyboard configuration as the LG Leon. There's a device tree. Google it. Google is your friend bro.
NASSTYROME said:
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Click to expand...
Click to collapse
not saying a official twrp isn't preferable, but man you got to learn how to talk to people, you were just short of cursing the dude out, and as far as the recovery the thing is solid(tested backup, flash and restore/ anyhow we got LGUP if you **** up so its not a huge deal), but anyone on this site shouldn't take someones word for things like recovery's and you should always test boot before you flash, also you don't seem to understand the first rule of xda-whatever happens to your device is on you, been that way since the og day's- talking politely to others is the way to go about things, people wont listen if you combative.
Kernel
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Didn't work, after selecting yes twice, my phone just starts like normal, doesn't go to TWRP or factory restore, it is there though because I can boot to it from the flashify app, ah well.
wait...my bad, I was highlighting the wrong one, lol, works great, thanks
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
callihn said:
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
Click to expand...
Click to collapse
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
[email protected] said:
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
Click to expand...
Click to collapse
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
callihn said:
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
Click to expand...
Click to collapse
I'm working on building it from source but keep getting errors and I'm trying it with another device that has Twrp (Moto E 2015) and followed the directions to the T and no luck. So I am trying......... Will let everyone know how it's going.
[email protected] said:
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Click to expand...
Click to collapse
kernel??????????????????????????
im down!
UPDATED 2/19/2018
Almost enough here to start attempting debug builds... any other builders/devs out there working on this device? Hopefully some of this will be useful.
Minimal Omni device tree for TWRP (full lineage branch in progress as of 2/19/2018)
https://github.com/mightysween/android_device_motorola_payton
Proprietary blobs/vendor (initial push 2/19/2018):
https://github.com/mightysween/android_vendor_motorola_payton
Partition names/locations/mounts...maybe a few missing still:
https://docs.google.com/document/d/1EkPOkc8uUStKIjRGC2-4jkcXpxmj8v3piGPqZi9ctQM/edit?usp=drivesdk
7.1 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/7.1.1-nougat-release-payton
8.0 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OPW27.57-40
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
gee one said:
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
Click to expand...
Click to collapse
There is no traditional recovery partition...handled by boot. A/B is mainly to allow 'seamless' updates (as in OTA that downloads to the other partition for instant reboot). Bit more to it... if you want to read more, check out the Pixel forums.
Well... progress is being made. Wish there were others (there must be!) working on this.
I have the stock kernel, a VERY basic device tree, and cobbled-together vendor... syncing repos and will try to compile TWRP over the weekend. I do not expect it to work
Dealing with this right now on brunch...runs fine up until this point, appreciate any thoughts:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfslollipop_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Click to expand...
Click to collapse
Do I really need the lollipop libs???? Especially if I just want to compile TWRP and not full omni. Ahhhhhhh....so much fun
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
UPDATE: oops, totally compiled it with the wrong kernel. Haha... working through some defconfig issues, but hopefully nothing too crazy.
mightysween said:
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
Click to expand...
Click to collapse
I hope you can do it! Is the first step to get backups and ROMs. I don´t have the phone yet, but later the normal version that is sell in México and want to flash the Android One version (previously anyone get it working).
I'm returning my Amazon version of this phone and getting Project Fi version. I am willing to help in testing.
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
mightysween said:
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
Click to expand...
Click to collapse
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
SR3TLAW said:
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
Click to expand...
Click to collapse
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
mightysween said:
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
Click to expand...
Click to collapse
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
i.snehal.kiran said:
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
Click to expand...
Click to collapse
Thanks, picked up 3 changes from here already... will test them out soon!
So, I have checked out several XDA threads on this Xiaomi device (tissot) and I think it is going to help quite a bit with the A/B issues.
I am still, unfortunately stuck on getting TWRP to boot. Boot.img compiles fine and I can extract it and see TWRP has replaced stock recovery in the ramdisk, but it will not boot into recovery.
Ideally, we need a way to boot a TWRP image without flashing anything... easier said than done with devices that have recovery baked into the boot image. But once that works, we can extract just the ramdisk from my build and write a script to patch it into the stock boot image from the temporary TWRP running on the device.
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Incredible! Looking forward to having a custom recovery!
mightysween said:
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Click to expand...
Click to collapse
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
f3r.and0 said:
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
Click to expand...
Click to collapse
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
mightysween said:
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
Click to expand...
Click to collapse
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
DiDGR8 said:
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
Click to expand...
Click to collapse
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
mightysween said:
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
Click to expand...
Click to collapse
This just came to my mind, since this phone has 2 partitions for boot etc. --
Code:
mmcblk0p44: boot_a SIZE:65536 blocks
mmcblk0p45: boot_b
can't we make backup of boot_b ? it will be same as boot_a but unmodified i think ? i mean, use magisk/cf-autoroot/whatever to gain root on boot_a. and make backup of boot_b. so in case if we want to receive update, just restore back boot_b.img to boot_a slot and update through ota ? that way we can practically make full backup which is unmodified. ofc this is until we have fastboot image available and working TWRP.
also it seems all x4's are having same kernel according to this thread. although their build time is different.
LineageOS 17.1 - Official
There is now an official LineageOS 17.1 build available for Ocean! This was not created by me. Most credit seems to be due to SyberHexen. I'm simply posting here because nobody else has done so.
Main Page
Installation Instructions
Greek2me said:
...LineageOS 17.1 - Official...
Click to expand...
Click to collapse
A tear of joy comes to my eye. Thanks for the heads up.
I've been using it daily and so far it's great. No bugs to report yet.
Greek2me said:
I've been using it daily and so far it's great. No bugs to report yet.
Click to expand...
Click to collapse
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
IronTechmonkey said:
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Click to expand...
Click to collapse
I'm glad I could reach you on time! I'll keep that in mind about the thread - thanks for the heads-up.
toddk63 said:
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
Click to expand...
Click to collapse
I would recommend that you try the installation again, taking care to follow the pre-installation instructions here. Additionally, I recommend that you wipe everything (system, data, internal storage, and cache) before attempting to install LOS.
Install went fairly smooth last night.
Have had a few times (usually when playing a video via the browser) that the "shutdown" popup will show. Phone reboots but the Lineage "corrupt" screen comes up. Hitting Try Again works and it boots successfully.
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
Click to expand...
Click to collapse
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
This is the latest twrp for this phone touch ishue should b fixed. Siberhexon updated twrp
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
Thanks, I've heard about issues with lock screen/encryption and would deal with that for testing purposes by disabling security before doing anything in TWRP. I may have to be content with re-flashing and restoring apps if anything breaks.
[EDIT] I saw that you added a link to a TWRP build.which is appreciated but I would first try the official one (twrp-installer-3.4.0-0-ocean.zip) which the LOS instructions indicate. If I did use an alternative I'd want to get it from a designated portal and know more about its origins.
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
IronTechmonkey said:
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
Click to expand...
Click to collapse
Well the official one is missing some things then one I posted whit h has no problems I use it
roadkill42 said:
Well the official one is missing some things then one I posted whit h has no problems I use it
Click to expand...
Click to collapse
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
IronTechmonkey said:
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
Click to expand...
Click to collapse
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
roadkill42 said:
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
Click to expand...
Click to collapse
Aaaahhhh, now you are making a connection to things I know. The fact that SyberHexen worked on it would be enough for me to trust it. In any event it is still best to link to the source rather than re-post (whenever possibe) so that people may see the trail and know what they are dealing with. Perhaps you could edit the post where you shared it, to say it came from some of the same devs that work on the ROM. With a note like that I would have had no doubts. In any event, I may wait for the patch to go official and work around the issue until then but it is good to know about. Thanks again for the tip and the tweaked version of TWRP.
[EDIT] Here is a direct link to the download: https://androidfilehost.com/?fid=8889791610682939639.
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Click to expand...
Click to collapse
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Greek2me said:
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Click to expand...
Click to collapse
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
IronTechmonkey said:
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
Click to expand...
Click to collapse
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
I'll be making new devdb posts for official G7 ocean/channel..
once threads are active please post there.
Thx
SyberHexen said:
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
Click to expand...
Click to collapse
That's what I was fishing for. There may be a chance I don't have to exchange device but if so that's what I'll do. Thanks for the coaching and for the work on Moto devices, especially the G7 Power.