Related
Hello All,
NOTE: You should unlock your bootloader.
These are patched TWRP recovery images for the Apollo and Thor devices only. Now Built from the latest .4.5.3 sources.
WARNING:
- Be sure to have a working /system partition before proceeding with installation.
Installation
- Ensure you are running stock firmware .3.2.3.2
- Obtain Root
- Copy the recovery image to the root of your sdcard
- Flash the recovery image by issuing the following commands:
Code:
adb shell
su
dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Download
- Apollo Recovery Image
- Thor Recovery Image
Thanks
- @vortox for the exploit
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
r3pwn said:
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
Click to expand...
Click to collapse
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
vortox said:
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
Click to expand...
Click to collapse
Ah.
I wrote the recovery on my apollo device which is running 14.3.2.3.2_user_323001720 version and it appears to work flawlessly. I booted into recovery (TWRP) successfully and rebooted the system successfully as well. Awesome!
Thanks for the feedback, glad it's all working
I haven't got a device at the moment to try it out on.
Sent from my Kindle Fire HDX using Tapatalk
Thanks ggow. Could we expect CM roms soon from your new release?
Working on 14.3.1.0
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
Hello tuanda82,
It depends on Amazon, my unlocked Apollo stopped working so they sent me a new one but came pre-installed with 4.5.2.
They have refused to downgrade me back to the old firmware. And after a lot of to and fro they agreed to replace it again .
I hope I have luck with the new device been on the required firmware.
But yes I definitely would like to make such a release.
dangerous
jeryll said:
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
Click to expand...
Click to collapse
I would not be trying interchang eROMs and or backups ppluntil certain things are verified by our developersgosh it only takes a few minutes to understand that one is built for locked bootloader the other one bypasses and they both flash completely different partitions and have different installation scripts.you're just asking to be one of the ignorant whiners on the sidelines while we have fun ..stuck with your brick. be patient guys this is all new stuff if you can't afford to be a developer then I devise you let somebody else take the risk
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
tbm13 said:
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
Click to expand...
Click to collapse
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
r3pwn said:
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
Click to expand...
Click to collapse
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Håvi said:
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Click to expand...
Click to collapse
Flash the rollback image to stock slot. This will then enable you to get back to 3.1.0
ggow said:
Flash the rollback image to stock slot. You need to be on stock version < 3.2.4.[/QUOT
Edit, found answer in OP
Click to expand...
Click to collapse
I was able to roll back to 3.1.0 and installed twrp. I was able to make a backup and successfully restored the backup. However after about an hour I came back to my kindle an noticed it updated itself to 4.1.1. I was under the impression with recovery installed any new updates would . Not be able to install. Now when I try to boot into recovery it on l y boots kindle recovery not twrp.
Sent from my KFAPWI using Tapatalk
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
GSLEON3 said:
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Click to expand...
Click to collapse
Thanks gsleon but don't rob your mom
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
ggow said:
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
Click to expand...
Click to collapse
Crossing fingers
Thanks goes to @nilezon for giving me the rundown, as it is all from his repos, save for a couple of things to make it work for the Z5 instead.
(Yes, your bootloader has to be unlocked)
Kernel is based on firmware version 32.0.A.6.152
There is two versions of the kernel: one with a recovery script, and one without.
The one with the recovery script will allow you to boot into recovery during your phone's startup process.
To enter recovery:
Boot up your phone like normal. Wait for the LED status light to turn amber. Once that happens, start pressing the volume buttons a few times. This will take you into the recovery menu.
The one without the recovery script does not have this option. This means that your phone will boot up a few seconds faster than the one with it.
Xposed: The Camera 2.0.apk plays nicely with Xposed now. No need to deoxed it manually!
Anyways:
TWRP
https://goo.gl/k9PiFV - TWRP 2.8.7.0
KERNELS
https://goo.gl/wzUAv4 - With recovery script, flashable zip file
https://goo.gl/8LTc9l - No recovery script, .img file that must be flashed through fastboot
For the recovery:
Code:
fastboot boot recovery.img
to just boot into it to flash a zip
OR
Code:
fastboot flash recovery.img
to flash it (although, you will need to do fastboot boot recovery the first time to get into it)
Kernel:
Code:
fastboot flash boot z5_stock_fixed_fixed.img
- For the .img file
The blues are oranges instead, like his, but it is kinda cute.
Have fun.
For unlocked bootloaders?
Sent from my Sony Xperia Z5
Snaqejack said:
For unlocked bootloaders?
Sent from my Sony Xperia Z5
Click to expand...
Click to collapse
Yes.
Technically you can flash the boot.img in the recovery ?
bazhip said:
This isn't flashable, only bootable:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
nilezon said:
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
Click to expand...
Click to collapse
I saw that at the bottom of your post right afterwards I'll modify it in a bit here, but I wanted to make sure it was going first. Thanks for making that script!
Thanks, bazhip.
Can you provide the modified source and a quick run through on how to compile it on github?
yannik~ said:
Thanks, bazhip.
Can you provide the modified source and a quick run through on how to compile it on github?
Click to expand...
Click to collapse
The kernel or TWRP? I'm kinda busy though so I'm not sure when I'll get around to it. If you want, look at the dirty ROOT thread for nizelion and my posts. I was pretty vocal about the process and what I was doing, as it was my first time ever doing it. You should be able to follow it, I think.
Were the only changes you made disabling SONY_SECURITY_RIC and DM_VERITY in the defconfig?
zwliew said:
Were the only changes you made disabling SONY_SECURITY_RIC and DM_VERITY in the defconfig?
Click to expand...
Click to collapse
That, and ro.secure disabled and ro.debuggable enabled. As close to stock as possible.
bazhip said:
Thanks goes to @nilezon for giving me the rundown, as it is all from his repos, save for a couple of things to make it work for the Z5 instead.
(Yes, your bootloader has to be unlocked)
Anyways:
https://goo.gl/k9PiFV - TWRP 2.8.7.0
https://goo.gl/8LTc9l - Kernel that I compiled that allows root
This isn't flashable, only bootable:
Code:
fastboot boot recovery.img
Kernel:
Code:
fastboot flash boot z5_stock_fixed_fixed.img
The blues are oranges instead, like his, but it is kinda cute.
Have fun.
Click to expand...
Click to collapse
Can it be use on E6683
Build no - 32.0.A.6.152
winkhant said:
Can it be use on E6683
Build no - 32.0.A.6.152
Click to expand...
Click to collapse
It's built for the 6653, but I think it should work for the 6683. Give it a shot. If it doesn't, just flash back the stock kernel.sin from the ftf.
winkhant said:
Can it be use on E6683
Build no - 32.0.A.6.152
Click to expand...
Click to collapse
I've applied this on my E6683. All looks good :good:
magadaner said:
I've applied this on my E6683. All looks good :good:
Click to expand...
Click to collapse
Awesome! That's what I figured, but good to have confirmation. I'll edit accordingly.
nilezon said:
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
Click to expand...
Click to collapse
Is there anything that needs to be changed with the recovery script to work on the Z5? I threw it into my kernel and followed the directions to a tee and I get a bootloop. I saw @AndroPlus made a kernel too using your script, so I flashed it to see if it worked and it was fine. I unpacked his boot.img and looked at it and the structure was the exact same. After hitting my head against a wall for a while, I tried repacking his just to make sure I wasn't crazy. The file size between his initial boot.img and the repacked one was a few KB different, and when I repack his, it bootloops too. So then I made sure mkboot tools were working fine and I unpacked/repacked my initial kernel, and it boots just fine.
Then I tried breaking it down:
I took my kernel, unpacked/repacked and it was fine. Then I copied over the bootrec folder, repacked, and it was fine. Then I made sure the symlink was working, so I:
Code:
mv init init.real
ln -s init.real init
and it booted just fine.
Then I did the final
Code:
rm init
ln -s /bootrec/init.sh init
and repacked, and it bootloops forever Any ideas about what is happening?
The only thing I can think of is that I messed up the symlink some how, but I dont know why AndroPlus's works before repacking and not after. Bleh :/
EDIT: **** everything. I ended up using SuperRs kitchen instead. That worked just fine. Noooo idea why mkbootimg_tools failed me.
External SD card is not detected on E6683.
Masa. T said:
External SD card is not detected on E6683.
Click to expand...
Click to collapse
Once I get my Z5 dual (E6683) in I may try to build a kernel specifically for the E6683's. I need to figure out how much I'll lose from losing the DRM keys.
Masa. T said:
External SD card is not detected on E6683.
Click to expand...
Click to collapse
In the kernel or TWRP?
EDIT: My bad, I spaced on the variants. I thought the 6683 was the baseband variant, not the dual sim. Yeah, I wouldn't roll with this on there.
And this is confirmed as working on the Z5 ?. because I have waited for root for this for some time now, and if it works I will be a happy man.
MeX_DK said:
And this is confirmed as working on the Z5 ?. because I have waited for root for this for some time now, and if it works I will be a happy man.
Click to expand...
Click to collapse
This is not an exploit, if that is what you are asking. As stated in OP, you need to unlock your bootloader first. The kernel is merely the stock kernel with the security features disabled, which allows you to be able to flash SuperSU. But yes, it works.
Since no guide has been updated with information on official TWRP for root and backup reasons, I thought I'd create one.
DISCLAIMER:
To do this method requires you to unlock your bootloader. Your warranty is now void. This method assumes you have basic knowledge of ADB and Fastboot commands and know how to recover your device if you accidentally type a wrong command and now boot to TWRP and can't boot to system. If you cannot recover from this, Read up on guides to "return to stock" and familiarize yourself on how to recover your device should something go wrong.
There are two methods for root. You can flash TWRP to your boot image to be able to reboot to TWRP without a PC, or just a temp boot so you can just have root and not TWRP. I'll put in brackets the minor differences.
1: Get ready
Download latest build of TWRP img file from their website.(Previous link is to their instructions and device specific patches, download page is HERE.) {download the latest zip if you want to flash TWRP}
Download what you want on your phone (SU, Magisk, etc)
2:
Hook phone up to your PC, be sure you have latest adb/fastboot drivers. (I do not support windows related questions. If you have latest drivers, you'll have no issue with the below commands, Linux just works for this kind of thing)
3:
Navigate to your directory that has that img downloaded. (windows, shift right click and say "open command prompt here")
Type the below commands, and terminal output should be similar: (I.E. this is a copy/paste of terminal)
Main thing to remember is "Fastboot boot {filename}.img"
Code:
[email protected]:~$ adb reboot bootloader
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ fastboot boot twrp-3.2.1-1-nash.img
downloading 'boot.img'...
OKAY [ 0.841s]
booting...
OKAY [ 5.135s]
finished. total time: 5.976s
[email protected]:~/Downloads$
BE SURE TO DO BOOT AND NOT FLASH!!! (If you ask why you can no longer boot to system, I'll let you know you missed this line.)
5:
You're now in TWRP!
It will ask you for your password. This is your PIN or password to unlock your phone. Enter it.
TWRP has now decrypted your storage to read the zip file(s) you put on your phone!
Go to install and navigate to your directory where you put that file
Install Magisk/SU/TWRP/whatever you please.
(Note: some root zips require a factory reset)
6:
Reboot!
You're Done congratulations!
Attached are images if they help you see you're doing the right thing.
Special thanks @erfanoabdi @invisiblek @npjohnson @joemossjr @jbats
Without the above people a lot of what's above woudn't have been possible for this device specifically. Also, thanks to everyone who pitched in to get a device over to invisiblek. Leaps and bounds have been done since that donation. And thanks to the other devs who have invested in this phone and their time to help out.
(Quoted from Nathan Chance)
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Random issues post:
SU does some wonky edits to the ramdisk. It is highly suggested to flash Magisk for root.
Some have reported needing to wipe data after flashing Magisk. If you can't boot after flashing Magisk, just go back into recovery (can be twrp or stock) and wipe data/factory reset to boot again.
Note: we do not have a recovery partition. Never flash the img file! Download the flashable zip if you want twrp on your phone and flash per OP instructions.
Awesome thanks
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
droidgreg said:
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
Click to expand...
Click to collapse
Be sure to mount system under the "mount" button
I need the OCX27.1 oreo. I did a return to stock flashall to OCX27 and now reflashed TWRP and Magisk and boots fine but I lost baseband and IMEI
Added warning to OP that some root zips require a data wipe.
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
will4958 said:
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
Click to expand...
Click to collapse
This guide assumes you can unlock your bootloader. Since Verizon and AT&T feel they have a right to lock down their devices, this guide won't work. That is why I voted with my wallet and left Vz after my M7 due to them putting phone OEM's privates in a vice and forced them to lock out those carrier variants.
Has this method been tested with OCX27.1 Oreo on TMO?
droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
It probably hasn't been tested, but it should work in theory.
Uzephi said:
It probably hasn't been tested, but it should work in theory.
Click to expand...
Click to collapse
I was on 27.1 when I attempted to root and got into a bootloop and lost my baseband when I flashall back to stock OCX27. I have a feeling 27.1 update isn't compatible with this method and cannot be downgraded to even OCX 27 Oreo
so no go on 27.1 twrp? I have root on 27.1 TMO obtained post update. Obtained by fastbooting the nash twrp and running magisk 16.zip. No needing to format data or anything
I was just wondering about the installable twrp zip. I am coming from samsung development so all this A/B partitioning and some of the other partitions are new to me.
As soon as I can get twrp on the phone and feel comfortable recovering. The kernels and roms will start coming.
Feels strange not having odin to save my ass
droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
tested and working
mattlowry said:
tested and working
Click to expand...
Click to collapse
Have you actually flashed installer.zip to install TWRP or just booted TWRP and only flash magisk or SU for root without installing TWRP?
I fastboot booted the twrp. I didn't try the installer. What is it?
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
luponcooper said:
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
Click to expand...
Click to collapse
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Uzephi said:
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Click to expand...
Click to collapse
Thanks a lot uzephi for answering.
I have the 6gb ram and 64gb model, XT1789-05. I try whit no succes to install Magisk (Error1) so i made a factory reset but still doesn't boot, stays in M logo.
Im super noob, can you guide me? i dont know how to recover the boot.img.
excuse my english.
$50 available via the crypto currency of YOUR choice.
Request: root. Tethered root is ok. Magisk systemless safteynet passing persistent root via zip flashing using persistent twrp is preferred, naturally.
This phone is AMAZING. Also the one sold from motorola.com is bootloader unlockable. The Amazon one is not.
To verify: if you got your z3 play from carrier or Amazon it is not bootloader unlockable.
If you bought from Motorola.com it is bootloader unlockable.
Battery without Moto mod is the best I have ever seen. Screen is amazing. Microsd slot, this is a really good feature. This is what my s9 plus should have been. No bloatware. I only want root for systemwide adblocking. (Adguard systemstore certificate)
With the Moto battery mod you can't run out of battery in a day. It's the best. Hopefully we will get unofficial custom rom someday so I can use Xposed and microg. You would be surprised how much telemetry even "stock like" roms have.
tomkleeeb said:
$50 available via the crypto currency of YOUR choice.
Request: root. Tethered root is ok. Magisk systemless safteynet passing persistent root via zip flashing using persistent twrp is preferred, naturally.
Click to expand...
Click to collapse
An attempt was already made. Using the firmware image someone linked here, I attempted to build and flash a TWRP for the Z3 Play I bought from Best Buy.
The result was a hard brick. Device would no longer power on. (Never seen this before, so it was definitely worth documenting for the TWRP chat)
Got a replacement Z3 Play, rebuilt TWRP but booted the firmware. Hard hang. Tried booting just the boot.img from the firmware image... also a hard hang.
So the software that we have now is not compatible with the Z3 Play.
Root and TWRP will come easily once we have an official image for the phone. It's unlocked, that's usually the hard part. Just gotta wait for Motorola to release the files or source first.
twelfth said:
An attempt was already made. Using the firmware image someone linked here, I attempted to build and flash a TWRP for the Z3 Play I bought from Best Buy.
The result was a hard brick. Device would no longer power on. (Never seen this before, so it was definitely worth documenting for the TWRP chat)
Got a replacement Z3 Play, rebuilt TWRP but booted the firmware. Hard hang. Tried booting just the boot.img from the firmware image... also a hard hang.
So the software that we have now is not compatible with the Z3 Play.
Root and TWRP will come easily once we have an official image for the phone. It's unlocked, that's usually the hard part. Just gotta wait for Motorola to release the files or source first.
Click to expand...
Click to collapse
Can you dump boot.img from the same devise, then fastboot boot boot.img?
If that works...
Could you then use magisk to add systemlessly root to the boot image
Then fastboot boot patched boot.img for tethered root?
This thread shows dumping partitions
https://forum.xda-developers.com/showthread.php?t=2450045
tomkleeeb said:
Can you dump boot.img from the same devise, then fastboot boot boot.img?
Click to expand...
Click to collapse
Not without root.
tomkleeeb said:
This thread shows dumping partitions
https://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Also from that thread:
TheThread said:
Pr-requirement:
- Rooted device.
Click to expand...
Click to collapse
You need root to get boot.img from a device to build TWRP.
or.
You need firmware images to be released by Motorola to build TWRP with the boot.img they release.
or.
You need source.
No way around it.
twelfth said:
You need source.
No way around it.
Click to expand...
Click to collapse
I made a thread on their official forums. https://forums.lenovo.com/t5/Moto-Z...this-phone-D/m-p/4176309/highlight/false#M200
This may seed things along.
if you boot into bootloader and run fastboot getvar all you'll see that our firmware is based on LA.UM.6.2.r1-07200-sdm660.0
so this should be our (incomplete) kernel source
https://source.codeaurora.org/quic/la/kernel/msm-4.4/tag/?h=LA.UM.6.2.r1-07200-sdm660.0
search for LA.UM.6.2.r1 on https://wiki.codeaurora.org/xwiki/bin/QAEP/release and you'll see all the updates we're missing since march
frantisheq said:
if you boot into bootloader and run fastboot getvar all you'll see that our firmware is based on LA.UM.6.2.r1-07200-sdm660.0
so this should be our (incomplete) kernel source
https://source.codeaurora.org/quic/la/kernel/msm-4.4/tag/?h=LA.UM.6.2.r1-07200-sdm660.0
search for LA.UM.6.2.r1 on https://wiki.codeaurora.org/xwiki/bin/QAEP/release and you'll see all the updates we're missing since march
Click to expand...
Click to collapse
I posted on GitHub asking for source.
Anyone wanna bump it?
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165
i have patched boot.img for 1929-8 using magisk manager apk from magisk 16.7.
not tested, i have locked bootloader.
if you have unlocked bootloader you can try "fastboot boot patched_boot.img" first without flash to see if it even boots. if it does you can try to flash it, extract magisk 16.7 zip and install apk from common folder.
https://drive.google.com/open?id=1n7Wf8ekChsDIUFmya0yFIRFQ581EIQxZ
if you brick your device you're on your own.
also i have sent boot.img to TWRP Builder, hopefully guys there can make a port from it.
frantisheq said:
i have patched boot.img for 1929-8 using magisk manager apk from magisk 16.7.
not tested, i have locked bootloader.
if you have unlocked bootloader you can try "fastboot boot patched_boot.img" first without flash to see if it even boots. if it does you can try to flash it, extract magisk 16.7 zip and install apk from common folder.
https://drive.google.com/open?id=1n7Wf8ekChsDIUFmya0yFIRFQ581EIQxZ
if you brick your device you're on your own.
also i have sent boot.img to TWRP Builder, hopefully guys there can make a port from it.
Click to expand...
Click to collapse
I have 1929-4 and unlocked the bootloader, tried it all, it's useless. (I used the boot of course from my version) Also I tried to port twrp but beyond the splash screen with the inscription twrp it did not work, and my knowledge in programming is almost equal to 0.
thought so. stock boot.img should boot with locked bootloader and it didn't.
ok i'll try to capture OTA url when it's available.
And yet I managed to get the root of the right through the magic and actually boot it. It was necessary in the magic to choose options for patch boot as far as I remember with encryption related, and it worked out))
frantisheq said:
thought so. stock boot.img should boot with locked bootloader and it didn't.
ok i'll try to capture OTA url when it's available.
Click to expand...
Click to collapse
Moto asked what version I need.... What version do we need to build root? https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165
this looks looks like a bad joke. we don't even need to ask them, there's GPL
frantisheq said:
this looks looks like a bad joke. we don't even need to ask them, there's GPL
Click to expand...
Click to collapse
I don't know. I just want root.
I think they can get away with it because source is available upon request, but no one requests it. I am surprised their GitHub doesn't have 1000s of people clamoring for source code for root. This thing is on my short list of phones. Op6/6T would be my next choice but I like microsd more than I like root friendly warrenty.
tomkleeeb said:
I don't know. I just want root.
I think they can get away with it because source is available upon request, but no one requests it. I am surprised their GitHub doesn't have 1000s of people clamoring for source code for root. This thing is on my short list of phones. Op6/6T would be my next choice but I like microsd more than I like root friendly warrenty.
Click to expand...
Click to collapse
Try to boot from my boot (fastboot boot root.boot.img) and if the system boots,you will see in the manager of magics that you already have the root rights, then you can safely flash this boot to yourself (fastboot flash boot root.boot.img) and it will be your root. But twrp recovery I can not yet port unfortunately.(And of course you need to have a bootloader unlocked)
https://drive.google.com/file/d/1wwD4J3DN4sYqfD1hOe0uApHC9tgqKIfu/view?usp=drivesdk
Willy33 said:
Try to boot from my boot (fastboot boot root.boot.img) and if the system boots,you will see in the manager of magics that you already have the root rights, then you can safely flash this boot to yourself (fastboot flash boot root.boot.img) and it will be your root. But twrp recovery I can not yet port unfortunately.(And of course you need to have a bootloader unlocked)
https://drive.google.com/file/d/1wwD4J3DN4sYqfD1hOe0uApHC9tgqKIfu/view?usp=drivesdk
Click to expand...
Click to collapse
Have to buy the phone first lol.
No root = no buy
I just like the idea of the ga!epad controller mod $79.99
Android has no good game controller
kernel source should be released by tuesday
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165#issuecomment-415027775
i have paid to download firmware for XT1929-8 and unlocked the bootloader.
the bad news, boot.img patched with Magisk won't boot, it just reboots.
the good news, stock boot.img worked so my phone works.
the best news, treble ResurrectionRemix system img for ARM64 a/b with gapps and su just booted up
https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299
i'm going to try pixel experience later
EDIT: sound works, dual sim works, wifi works, fingerprint works, navigation bar needs to be enabled in settings, battery moto mod seems to be not charging, unable to change display brightness
pixel experience won't boot (maybe it will, it's because i have downloaded a version instead of a/b). i'm back to stock ROM
EDIT2: got root working.
not sure if it's needed but i have used Magisk Manager from https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
installed the apk
set up that URL as custom Update Channel in Magisk manager settings
patched boot.img with "Preserve force encryption" and "Preserve AVB2.0/dm-verity" checked
patched boot.img for xt1929-8 can be downloaded here https://drive.google.com/open?id=11CJ65ojDZmCQVZGSHXicfFSMaenFHiiv
now where is that $50? my donation button still works
EDIT3: got boot.img with working TWRP, but it won't boot Android just TWRP.
if you'd like to try fastboot flash boot_a recovery.img and choose recovery in bootloader menu.
be sure to have boot.img backup before flashing because it won't boot Android and TWRP is unusable as it is, it can't even mount data.
https://drive.google.com/open?id=1C3lcyK3y4RL1Ep56wqWpfw0VWIHuhiO0
Absolutely all the same thing I did with my 1929-4 three days ago ... with twrp the same situation unfortunately ...
i was able to flash magisk and boot.img so it works. still don't know why it won't boot android.
device/motorola/beckham - https://drive.google.com/open?id=1KQ8KFthPJzr1VXt41F9N7O7fY8IRzcb6
DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff.
What has been tested and works:
- Touchscreen
- Installing flashable zips
- Flashing images
- Flashing the recovery itself
- Creating backups (to internal storage, sdcard or OTG)
- Restoring from backups
- Terminal
- adb
- Rebooting to system, recovery, bootloader, ...
That doesn't mean that other things don't work. It just means they weren't tested yet. As I proceed with testing I will update the above list.
Usage (without flashing)
Bash:
# boot to bootloader
adb reboot bootloader
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
If you want to flash you have 2 options
Bash:
# boot to bootloader
adb reboot bootloader
# ********* OPTION 1 *********
# Flash to active slot (replace <slot> with either a or b, depending on the current active slot).
# Of course, you can flash to both by first specifying a and then b.
fastboot flash recovery_<slot> twrp-3.5.2_10-kiev.img
# ********* OPTION 2 *********
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
# Once in the recovery, copy the twrp image file to your internal storage
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
# Then go to Install, then Install image, select the twrp image you pushed before.
# Then select the Recovery partition and swipe to confirm.
# Before swiping you will have the option to decide if you want to flash to both slots.
Download: google drive
Sources will be posted in due time and this post will be updated accordingly.
Built for: Motorola Moto G 5G (Motorla One 5G Ace)
My model: XT2113-3 (kiev)
Credits
To the guys over here for the device tree, especially to SyberHexen for providing me with useful information.
reserved
reserved
Great!
Tested on my Moto G 5G XT2113-3. Seems to work properly. Good job. Awaiting to flash it.
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
It won't brick. I used it. (only once)
clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
h3xmind said:
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
Click to expand...
Click to collapse
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Tomspector said:
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Click to expand...
Click to collapse
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me.
I will do it now,
I would help
h3xmind said:
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me
Click to expand...
Click to collapse
I will do it now
Tomspector said:
I will do it now,
I would help
I will do it now
Click to expand...
Click to collapse
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Tomspector said:
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Click to expand...
Click to collapse
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
h3xmind said:
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
Click to expand...
Click to collapse
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Ok, thanks for your help. I won't be testing anything tomorrow. I have a day off with my family
Tomspector said:
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Click to expand...
Click to collapse
Should be here: https://mirrors.lolinet.com/firmware/moto/kiev/official/
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Anyway, I flashed it by doing the following:
Bash:
# boot to bootloader
adb reboot bootloader
# boot to twrp
fastboot boot twrp-3.5.2_10-kiev.img
# push the recovery image to the Download folder
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
Once inside the recovery I went to Install, then Install image, once I selected the twrp-3.5.2_10-kiev.img file that I previously pushed, twrp asked me on which partition I would like to flash it. I selected the Recovery partition. (Although I ask myself why does the phone have a separate recovery partition if it is an A/B device. I still have to figure this out. Normally in these devices one would have to pack the recovery into the boot imate and than flash the whole thing to the boot partition.)
Then I rebooted to recovery and it took me directly to twrp. The problem, however, is that the touch screen didn't work anymore. So, I guess I got myself some extra work But it'll be fun. I can't wait to put my hands on it.
Did you manage to find the rom for your phone?
PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
I tried Hexen's recovery. It's easily fixable to make the touch work. It took me two minutes. I'll let the guys working on it know how to do it. But first I have to figure out why does the touch screen stop working once you flash the recovery.