Experimental twrp for moto one vision (need tester)
Requirements: Bootloader Unlocked
Before installing, test using "fastboot boot TWRP_Kane.img"
link: https://drive.google.com/file/d/1vhNiSuvB99j69wjNXoJn4dycpjUtKkTI/view?usp=drivesdk
I can test it this weekend
I wish I could try it right away, but I'm away from home over the weekend and I left my one vision at home.
can do, sir
---------- Post added at 01:02 PM ---------- Previous post was at 12:52 PM ----------
"Validation image failed"
Booting via fastboot failed.
I'm new to this, contact me any time if you need more info.
Alisson1397 said:
Experimental twrp for moto one vision (need tester)
Requirements: Bootloader Unlocked
Before installing, test using "fastboot boot TWRP_Kane.img"
link: https://drive.google.com/file/d/1vhNiSuvB99j69wjNXoJn4dycpjUtKkTI/view?usp=drivesdk
Click to expand...
Click to collapse
I tried it but I'm getting this error:
Sending 'boot.img' (36236 KB) OKAY [ 1.170s]
Booting FAILED (remote: '')
fastboot: error: Command failed
On bootloader screen it says "Validation image failed"
On adb screen says :
C:\Users\dml02\Downloads>fastboot boot TWRP_Kane.img
downloading 'boot.img'...
OKAY [ 0.825s]
booting...
FAILED (remote failure)
finished. total time: 0.991s
"Validation image failed" on my device.
If anyone knows how to fix the error, please help!
Alisson1397 said:
If anyone knows how to fix the error, please help!
Click to expand...
Click to collapse
sorry to ask mate. Are you the dev of this twrp image?
AndresOrue said:
sorry to ask mate. Are you the dev of this twrp image?
Click to expand...
Click to collapse
Yes, I compiled it, but found a device tree ready for twrp
I made a device tree for this device, successful kernel and twrp compilation, but still the same error as above.
Guys, is it worth the wait for working twrp for motorola one vision?
Tuldon said:
Guys, is it worth the wait for working twrp for motorola one vision?
Click to expand...
Click to collapse
I was near to buy one for developments, I didn't due to his price now is 274 euro was 240 but I arrived too late, it's too high for android one phone :/ .
Tuldon said:
Guys, is it worth the wait for working twrp for motorola one vision?
Click to expand...
Click to collapse
haky 86 said:
I was near to buy one for developments, I didn't due to his price now is 274 euro was 240 but I arrived too late, it's too high for android one phone :/ .
Click to expand...
Click to collapse
Yep, this phone is too expensive and a waste of time. I regret I bought it
I'm in the same situation with my Motorola One Action. I'm looking in both forums because they're almost the same phone (same SoC, different camera config and codename; Vision is Kane and Action is Troika).
I managed to get the stock firmware for my One Action XT2013-1, grabbed the boot.img, patched on Magisk, unlocked the Bootloader and tried to boot the patched image with the same error described in this post "Validation image failed" on device and "Failed" on fastboot.exe.
We need to bypass that validation so we can boot unsigned images on our phones. Sadly, I'm not a developer but will happily test any advance on my device.
Greetings.
From what I know "Validation image failed" error comes up if you haven't unlocked the bootloader or if the firmware you're trying to flash is older than your current firmware.
Did you enabled the "OEM unlocking" toggle from the developer settings? This might block the twrp installation.
@Alisson1397 also are you sure that the source code you're using for this twrp is for our particular device?
SnoopDoggyStyleDogg said:
From what I know "Validation image failed" error comes up if you haven't unlocked the bootloader or if the firmware you're trying to flash is older than your current firmware.
Did you enabled the "OEM unlocking" toggle from the developer settings? This might block the twrp installation.
@Alisson1397 also are you sure that the source code you're using for this twrp is for our particular device?
Click to expand...
Click to collapse
Use this device tree to compile TWRP
https://github.com/AlissonGrizotti/TWRP-device_motorola_kane
Maybe I'm using an outdated boot.img, but I find it unlikely
Related
Is anyone working on a method for rooting that does not require an unlocked bootloader?
Nope no chance without unlocked bootloader
Gesendet von meinem EndeavorU mit Tapatalk 4
Okay and how some androidphone have been rooted without an unlocked bootloader ? Defy for example.
I don't own the Moto G, but it is possible to root with a locked bootloader. You gonna need to set up adb and fastboot on your pc using Android SDK. You will also need twrp. There are some guides on how to set up and use adb and fastboot.
Twrp can give you root permission if you don't have it. Hope this helps a bit.
Sent from my Huawei Ascend P1 U9200 using xda app-developers app.
How about:
"Fastboot boot recovery.img" CWM, then you can flash the superuser zip without unlocking the bootloader or flashing a different recovery.
Lost, you have to set up adb and fastboot before you can flash a recovery.
Sent from my U9200 using xda app-developers app
I didn't mean to imply setting up adb was not required. And just to clarify, I was suggesting booting a recovery, not flashing it permanently.
lost101 said:
I didn't mean to imply setting up adb was not required. And just to clarify, I was suggesting booting a recovery, not flashing it permanently.
Click to expand...
Click to collapse
Sure, I thought you meant flashing.
Sp any info or update , if someone is working on rooting moto g without unlocking the bootloader??
I tried just booting a recovery once, but it ended up booting the empty stock recovery. I can try again in a few hours, but I'm not sure it'll work.
Sent from my XT1028 using Tapatalk
lightningdude said:
I tried just booting a recovery once, but it ended up booting the empty stock recovery. I can try again in a few hours, but I'm not sure it'll work.
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
Okay , You can try and tell us if it worked or not..
At least Someone is trying..
lightningdude said:
I tried just booting a recovery once, but it ended up booting the empty stock recovery. I can try again in a few hours, but I'm not sure it'll work.
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
Does not work.
@denzel09 is right, no matter how unhelpful his short answer was. It failed, and gave me this output.
Code:
C:\Android\sdk\platform-tools>fastboot boot TWRP2631_MotoG44.img
downloading 'boot.img'...
OKAY [ 0.360s]
booting...
FAILED (remote failure)
finished. total time: 0.365s
C:\Android\sdk\platform-tools>
lightningdude said:
@denzel09 is right, no matter how unhelpful his short answer was. It failed, and gave me this output.
Code:
C:\Android\sdk\platform-tools>fastboot boot TWRP2631_MotoG44.img
downloading 'boot.img'...
OKAY [ 0.360s]
booting...
FAILED (remote failure)
finished. total time: 0.365s
C:\Android\sdk\platform-tools>
Click to expand...
Click to collapse
You can not only simply to boot a custom recovery with locked bl on this phone. This is the problem. You can try all times you want but it ll not work unluckly.
denzel09 said:
You can not only simply to boot a custom recovery with locked bl on this phone. This is the problem. You can try all times you want but it ll not work unluckly.
Click to expand...
Click to collapse
Then why is it possible on other droids like SONY PHONES or earlier moto phones ..
is there any possibility of this in future ...??
galaxys2s said:
Then why is it possible on other droids like SONY PHONES or earlier moto phones ..
is there any possibility of this in future ...??
Click to expand...
Click to collapse
Boot a custom recovery with locked bl is not and will not possible on moto g. No matter if it's possible on other phones, we are talking about g.
If you want root without unlock bl you have only a way: to wait some exploit. For now there aren't, in future who know..
denzel09 said:
Boot a custom recovery with locked bl is not and will not possible on moto g. No matter if it's possible on other phones, we are talking about g.
If you want root without unlock bl you have only a way: to wait some exploit. For now there aren't, in future who know..
Click to expand...
Click to collapse
Yeah well, Hope some one will find a way a soon because not many people afford to lose warranty on rooting as unrooting will not save warranty..
Yep. Root is a risk for warranty.
For example, my two friends here in Italy, for different problems have send their g with unlocked bl in repair. Both are back repaired without any problems. So i mean that there are cases and cases. Btw root remains a risk for many.
denzel09 said:
Yep. Root is a risk for warranty.
For example, my two friends here in Italy, for different problems have send their g with unlocked bl in repair. Both are back repaired without any problems. So i mean that there are cases and cases. Btw root remains a risk for many.
Click to expand...
Click to collapse
That's lucky one actually , Hope every country have these type of care guys
---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------
mastergoga57 said:
You can do it without requiring to unlock bootloader but I am not sure of Moto g. I have done it for Samsung device but it should not make a difference as Moto g is another Android device.
You will need Android SDK and also need to run Twrp. It will do the job for you.
Click to expand...
Click to collapse
Have you tried it ??
Can you please test it as i have no moto g right now..
that's reason i m not buying currently,,
waiting for exploit...
Hi I just bought a XT1039 today and it came with the new 5.1 build out of the bos.
I've been reading the forums and it seems like there's no sure way to root and/or flash TWRP on Lollipop?
Does anyone know how I can do that? Or do I have to roll back to Kit Kat or something? Please help!
spencerchong said:
Hi I just bought a XT1039 today and it came with the new 5.1 build out of the bos.
I've been reading the forums and it seems like there's no sure way to root and/or flash TWRP on Lollipop?
Does anyone know how I can do that? Or do I have to roll back to Kit Kat or something? Please help!
Click to expand...
Click to collapse
I have the xt1045 and I'm in the same boat. If I find a solution, I'll let you know.
Okay, CF-Auto-Root worked! The batch file says a red android will show up.. never did, but it worked anyway.
http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406
I have twrp for xt1039 & superuser 2.48
Sent from my XT1039 using Tapatalk
---------- Post added at 10:51 AM ---------- Previous post was at 10:50 AM ----------
5.1 with twrp 2.8.7.0
Sent from my XT1039 using Tapatalk
This one works with 5.1.. I would install after rooting with the above method.
http://forum.xda-developers.com/moto-g/4g-development/collection-somcom3xs-experimental-corner-t2996266
Hey there, can anyone tell me whether or not I can just use the TWRP version that can be downloaded on twrp.me?
I have the XT1039 with a unlocked bootloader and I am aiming to install TWRP and later CM/ResurrectionRemix if possible onto the device.
But first things first - TWRP is the thing that is missing. Anyone still using the phone?
cyrrel said:
Hey there, can anyone tell me whether or not I can just use the TWRP version that can be downloaded on twrp.me?
I have the XT1039 with a unlocked bootloader and I am aiming to install TWRP and later CM/ResurrectionRemix if possible onto the device.
But first things first - TWRP is the thing that is missing. Anyone still using the phone?
Click to expand...
Click to collapse
TWRP for peregrine is available on twrp.me and it works fine - not sure what you mean with "missing".
Missing just personally on my phone
Alright thx will have a closer look!
I need to bother you again.
I have downloaded the latest twrp for the device but seem to be unable to get it up and running.
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (8374 KB)...
OKAY [ 0.293s]
writing 'recovery'...
OKAY [ 0.301s]
finished. total time: 0.596s
fastboot reboot
rebooting...
finished. total time: 0.004s
Looking good, but after that - when I press vol - & power on I get into the fastboot menu. When choosing "recovery" in there, the screen goes black and nothing happens.
Any idea?
edit: I get a "mismatched partition size (recovery)" within fastboot... didn't notice until now. Any input on that?
cyrrel said:
Looking good, but after that - when I press vol - & power on I get into the fastboot menu. When choosing "recovery" in there, the screen goes black and nothing happens.
Any idea?
Click to expand...
Click to collapse
No idea. It works fine on my XT1039. Try "fastboot boot twrp.img" to see if it starts that way. If it does, you could try copying twrp.img to the phone using adb push or mtp, then flash it to the recovery partition from twrp's "install image" feature.
cyrrel said:
edit: I get a "mismatched partition size (recovery)" within fastboot... didn't notice until now. Any input on that?
Click to expand...
Click to collapse
Yes, that's normal. Ignore it.
Thx but somehow I wasn't able to get into recovery but every time in the system itself. Recovery was overwritten, I think. After 20 or so tries I finally managed to get it running.
Thx for your help
cyrrel said:
Thx but somehow I wasn't able to get into recovery but every time in the system itself. Recovery was overwritten, I think. After 20 or so tries I finally managed to get it running.
Thx for your help
Click to expand...
Click to collapse
Hi
Do you have any links for the process you used on your phone
I also have a xt1039 that's stock and am looking around for a guide for my phone.
Cheers
Sent from my SHIELD Tablet K1 using Tapatalk
Hey there, basically this was a good base for me: https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine
cyrrel said:
Hey there, basically this was a good base for me: https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine
Click to expand...
Click to collapse
Thanks for that yeah that's got everything I need gonna have a go tonight...
Nothing much wrong with my stock rom just sick of it saying low storage so hoping marshmallow will sort that with using the sd card for internal storage
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
lazarus2297 said:
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
Click to expand...
Click to collapse
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
razrlover said:
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Click to expand...
Click to collapse
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
foosion said:
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
Click to expand...
Click to collapse
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
phonefreedom said:
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
Click to expand...
Click to collapse
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
lazarus2297 said:
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
Click to expand...
Click to collapse
+Natahranta had shared the following with me and I hope it helps in your case...
"Download factory image from Google, unpack it, insidebis another zip, there is boot.img file
Flash it to both slots A and B. It must be the same version/update your phone was on.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
If you're not sure which exactly stock rom build your phone is on, use the flash_all.bat to flash the whole image on your phone, to be sure you have no mismatch between system and boot. Just remove "-w" from the bat file so it doesn't erase your user data"
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
lazarus2297 said:
I have relocked the BL then booted into the OS
Click to expand...
Click to collapse
I don't have any suggestions for your issue. But don't relock it, ever. You are playing with fire, if it goes bad and it's locked you are done.
lazarus2297 said:
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
Click to expand...
Click to collapse
I had this problem and created a thread about it a month ago: https://forum.xda-developers.com/pixel-2/help/failed-remote-command-flash-error-t3701929. A couple other people in that thread are now also reporting the problem.
No one seemed to know what the " FAILED (remote: Command Flash Error)" means. I never figured it out.
At the time of the November update, however, I was able to sideload OTA images with adb without problem. I assume that the OTA method also updates the bootloader, like the Dev Preview did for you. I couldn't tell with the November update, though, because it had the same version of the bootloader in it as the one that shipped with the phone.
So I'm wondering if simply sideloading the current December OTA image with adb would accomplish the same thing you did, without having to lock the bootloader, unlock it again, and go through the pain of wiping the device. I wonder if there was just something weird about the original version of the bootloader. Weirdness like this was discussed early on with the Pixel 2 in this XDA article: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ If I'm right, then once one sideloads the December OTA image and gets a new bootloader, there may not be an issue flashing bootloaders with fastboot in the future. I assume that the Dev Preview also used the OTA method to update the device.
In other words, I'm wondering if the step of unlocking and relocking the bootloader was not necessary. You just had to do it to get the Developer Preview (right?).
Just guessing here. I haven't had time yet to try this.
Okay, I tried my idea above and I was correct. Simplying sideloading the December OTA image updates the bootloader. After that the problem is solved. I can successfully flash the bootloader .img file directly (from the factory image zip) using fastboot. So I assume going forward there should not be any problems flashing factory images, instead of sideloading OTA images.
This solution also avoids having to lock and unlock the bootloader and wipe the whole device in the process.
cb474 said:
Simplying sideloading the December OTA image updates the bootloader.
Click to expand...
Click to collapse
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
-----------
Nevermind. I figured out that recovery is part of boot now. I flashed the factory boot and flashing OTA now.
snovvman said:
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
Click to expand...
Click to collapse
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
cb474 said:
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
Click to expand...
Click to collapse
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
snovvman said:
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
Click to expand...
Click to collapse
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php
kendong2 said:
https://forum.xda-developers.com/showpost.php
Click to expand...
Click to collapse
That link leads to nothing.
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
snovvman said:
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
Click to expand...
Click to collapse
Yeah, I saw that. I'm just hoping with what was learned from the original Pixel and given that supposedly most phones will eventually use the A/B partition scheme that maybe TWRP will advance further on the Pixel 2. I really miss nandroid backups. I miss LineageOS too. Everything was so much simpler on my old Nexus 4. And I wasn't constantly feeling like I was going to brick my device every time I tried to do something.
cb474 said:
That link leads to nothing.
Click to expand...
Click to collapse
Sorry, did that on the phone. Was supposed to go here: https://forum.xda-developers.com/showpost.php?p=74704694&postcount=155
TWRP 3.2.0.0 final release (as I understand it) has been announced a few days ago. Don't know why the thread title still says beta.
This is freaking weird. Anyway, followed post #11 to sideload DEC OTA zip in stock recovery, and now finally I have a bootloader that is 0066 on both slot a and b. Thanked @cb474 !
Hello all!
I've recently submitted a GPL source request for the Moto Z4 (foles). Specifically for build PPF29.105-25-13. I'd like to gauge interest in releasing a port of TWRP for the Z4.
Update(10.08.19) - Kernel source has been released. I've started development of twrp for this device.
Thank You,
GirlsGoneAndroid
Count me in. I'm already modding mine like crazy TWRP is essential for me @ this point.
Yes, count me in too
Update!
Hello all!
I just wanted to give you an update. I've received word that the source code for the RETAIL version of the Moto Z4. Specifically version PPF29.105-25-13 will be released next week!
GirlsGoneAndroid said:
Hello all!
I just wanted to give you an update. I've received word that the source code for the RETAIL version of the Moto Z4. Specifically version PPF29.105-25-13 will be released next week!
Click to expand...
Click to collapse
That is wonderful news! I have my Bootloader Unlocked and ready to go! I am hoping this will eventually find its way to Linage OS
Thank You Very Much For Your Efforts GirlsGoneAndroid :good:
DrakeJones said:
That is wonderful news! I have my Bootloader Unlocked and ready to go! I am hoping this will eventually find its way to Linage OS
Thank You Very Much For Your Efforts GirlsGoneAndroid :good:
Click to expand...
Click to collapse
Thank you!
It looks like PPF29.105-25-13-2 got pushed out. Does anyone know what exactly the update contains? I haven't had a chance to check the changelog.
I've also reached out and requested PPF29.105-25-13-2 as well now that that's been pushed out.
GirlsGoneAndroid said:
Thank you!
It looks like PPF29.105-25-13-2 got pushed out. Does anyone know what exactly the update contains? I haven't had a chance to check the changelog.
I've also reached out and requested PPF29.105-25-13-2 as well now that that's been pushed out.
Click to expand...
Click to collapse
Yes I just updated, the release notes just say it updated the security patches through August 1st. Thats the only update it appears.
Grr I wish I had gotten the non vzw version. I'd be working on it now. But Verizon's deal was to good to pass up when it launched
Thank you for your efforts! Excited to get some root/custom roms soon
Does this help?
https://www.xda-developers.com/moto-z4-kernel-source-code/amp/
burnsky05 said:
Does this help?
https://www.xda-developers.com/moto-z4-kernel-source-code/amp/
Click to expand...
Click to collapse
Yes it does I'll be working on the port of TWRP this week.
If anyone is interested the direct link to the kernel source is https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PPF29.105-25-13
GirlsGoneAndroid said:
Yes it does I'll be working on the port of TWRP this week.
If anyone is interested the direct link to the kernel source is https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PPF29.105-25-13
Click to expand...
Click to collapse
Awesome I cannot wait, I miss root so much.
burnsky05 said:
Does this help?
https://www.xda-developers.com/moto-z4-kernel-source-code/amp/
Click to expand...
Click to collapse
"Motorola Moto Z4 kernel source code is now available"
YAY! WooHoo!
Lets Get This Ball Rolling! :highfive:
GirlsGoneAndroid said:
Yes it does I'll be working on the port of TWRP this week.
If anyone is interested the direct link to the kernel source is https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PPF29.105-25-13
Click to expand...
Click to collapse
This is really good. I'm on Z², waiting on root before I upgrade to Z⁴.
I cannot imagine buying a new phone without root.
sd_shadow said:
Try
https://mirrors.lolinet.com/firmware/moto/
Click to expand...
Click to collapse
This as well....
I've got a minimal twrp built. I have not had time to test it yet. Please do not flash it or install it yet! Only temporarily boot it to test it. I make no guarantees of safety. I'm not responsible for bricked devices...etc. If you'd like to help you can temporarily boot to it using these instructions.
Download twrp img
[URL Removed Test build did not work. removing for now.]
Boot your moto z4 to the bootloader (adb reboot bootloader)
Boot to the twrp image temporarily (fastboot boot foles.img)
If you are able to boot to the image please pull the recovery log! (adb pull /tmp/recovery.log)
Paste the recovery log to a pastebin website and post the link.
I'll continue to work on this throughout the week. Please only follow these steps if you're comfortable with adb/fastboot and can recover your phone to an operable state if something goes wrong.
GirlsGoneAndroid said:
I've got a minimal twrp built. I have not had time to test it yet. Please do not flash it or install it yet! Only temporarily boot it to test it. I make no guarantees of safety. I'm not responsible for bricked devices...etc. If you'd like to help you can temporarily boot to it using these instructions.
Download twrp img
https://mega.nz/#!aPZ3QQhD!XUA1ap6o0TPWD0kIxhH_a1PVg-Yc7ofqTZW3UdEToNg
Boot your moto z4 to the bootloader (adb reboot bootloader)
Boot to the twrp image temporarily (fastboot boot foles.img)
If you are able to boot to the image please pull the recovery log! (adb pull /tmp/recovery.log)
Paste the recovery log to a pastebin website and post the link.
I'll continue to work on this throughout the week. Please only follow these steps if you're comfortable with adb/fastboot and can recover your phone to an operable state if something goes wrong.
Click to expand...
Click to collapse
So I gave this a try today and I get the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot foles.img
downloading 'boot.img'...
OKAY [ 0.342s]
booting...
OKAY [ 10.238s]
finished. total time: 10.583s
Does not boot into TWRP and boots normally instead. Tried this many times with the same result. I have my bootloader unlocked and USB Debug enabled.
DrakeJones said:
So I gave this a try today and I get the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot foles.img
downloading 'boot.img'...
OKAY [ 0.342s]
booting...
OKAY [ 10.238s]
finished. total time: 10.583s
Does not boot into TWRP and boots normally instead. Tried this many times with the same result. I have my bootloader unlocked and USB Debug enabled.
Click to expand...
Click to collapse
Thank you for testing that out. I'll take a look at it over the weekend. I've gotten bogged down in school work.
TWRP can be created, but how do I install it?
vbmeta creates big obstacles for this...
ilia3367 said:
TWRP can be created, but how do I install it?
vbmeta creates big obstacles for this...
Click to expand...
Click to collapse
It's not that TWRP gets installed, you can boot to the recovery and then flash the zip file.
Install canary then update https://github.com/topjohnwu/Magisk
Then install this patch https://drive.google.com/file/d/11KaE0arOuqL6PUfV__CL4ajmqwxv1Skk/view?usp=drivesdk
Put this in fastboot folder
Then fastboot flash boot magisk_patched.img
google pay not working
jaythenut said:
Install canary then update https://github.com/topjohnwu/Magisk
Then install this patch https://drive.google.com/file/d/11KaE0arOuqL6PUfV__CL4ajmqwxv1Skk/view?usp=drivesdk
Put this in fastboot folder
Then fastboot flash boot magisk_patched.img
google pay not working
Click to expand...
Click to collapse
I do not have the P5 yet to test root.
To get Google Pay working, you need to hide play and pay services.
Also use system less for adware. (AdAway).
Sent from my Pixel 3a XL using Tapatalk
vandyman said:
I do not have the P5 yet to test root.
To get Google Pay working, you need to hide play and pay services.
Also use system less for adware. (AdAway).
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
Thanks
Adaway working a treat ?
It works thanks a lot
jaythenut said:
this patch
Click to expand...
Click to collapse
Can you tell us who made that patch. It might help some decide whether to trust it on their brand spanking new $1000 toy.
jaythenut said:
google pay not working
Click to expand...
Click to collapse
If you are lucky enough that Google hasn't yet turned on hardware attestation for you yet then you can use Magiskhide to get GP working (somebody else has already mentioned what you need to hide).
When, not if, they switch you over to hardware attestation you'll have 2 choices... Live without any app that requires your device to pass SafetyNet, or get rid of Magisk and relock your bootloader. (also hope that unlocking the bootloader on the pixel 5 doesn't trip some sort of fuse which makes it impossible to take things back to a pre-unlocked state)
I'm not going to root mine and I sincerely hope that you don't regret rooting yours.
Cheers.
Sent from my Pixel 5 using XDA Labs
SteveYoungs said:
Can you tell us who made that patch. It might help some decide whether to trust it on their brand spanking new $1000 toy.
If you are lucky enough that Google hasn't yet turned on hardware attestation for you yet then you can use Magiskhide to get GP working (somebody else has already mentioned what you need to hide).
When, not if, they switch you over to hardware attestation you'll have 2 choices... Live without any app that requires your device to pass SafetyNet, or get rid of Magisk and relock your bootloader. (also hope that unlocking the bootloader on the pixel 5 doesn't trip some sort of fuse which makes it impossible to take things back to a pre-unlocked state)
I'm not going to root mine and I sincerely hope that you don't regret rooting yours.
Cheers.
Sent from my Pixel 5 using XDA Labs
Click to expand...
Click to collapse
Hi mate I made the patch easy to do ?
And thanks for the info
Pixel 5, unlocked bootloader, rooted. Banking apps (tested: Germany BW Bank app & pushTAN app, Bosnia Unicredit Bank - all in one banking + token app) WORK with root and magisk hide (SafetyNet fails due to hardware attestation). Other apps that work while rooted with magiskhide regardles of attestation: PayPal, GooglePay (*due to a current issue with PayPal im not able to enable contactless payments with GPay at the moment, awaiting PayPal support reply, however the GPay app does launch and says that "Phone meets security requirements" despite SafetyNet failure.
With Magisk HideProps Module (Force Basic Attestation -> Pixel 3a) SafetyNet passes without issues.
GooglePay enabling contactless payments requires SafetyNet to pass. I added PayPal as contactless GPay option after passing SafetyNet. After enabling it I went on and restored the original Pixel 5 Fingerprint, didn't try paying anything this way yet tho. (If it passes like this, the HideProps would be a onetime thing, provided you dont add/remove cards often).
jaythenut said:
Install canary then update https://github.com/topjohnwu/Magisk
Then install this patch https://drive.google.com/file/d/11KaE0arOuqL6PUfV__CL4ajmqwxv1Skk/view?usp=drivesdk
Put this in fastboot folder
Then fastboot flash boot magisk_patched.img
google pay not working
Click to expand...
Click to collapse
What is the patch that needs to be installed? Just rooted without it and I don't see anything in particular not working (I flashed the whole image again and used that boot image with magisk).
matssa said:
What is the patch that needs to be installed? Just rooted without it and I don't see anything in particular not working (I flashed the whole image again and used that boot image with magisk).
Click to expand...
Click to collapse
Patch is there if you don't know how to patch the boot ?
didnt work here
Hi
It didnt work on my side.
Downloaded the Factory Image (not KKDI only) and patched with Canary Magisk MAnager
If I flash the patched img with the latest platform tools it says : FAILED (remote: Failed to write to partition Not Found)
If I use the Minimal ADB package it goes through, but does not install Magisk and root ^^
What am I doing wrong?
Thanks for your help
Frost Storm said:
Hi
It didnt work on my side.
Downloaded the Factory Image (not KKDI only) and patched with Canary Magisk MAnager
If I flash the patched img with the ADB driver it says : FAILED (remote: Failed to write to partition Not Found)
If I use the Minimal ADB package it goes through, but does not install Magisk and root ^^
What am I doing wrong?
Thanks for your help
Click to expand...
Click to collapse
Use my patch in first post ?
jaythenut said:
Use my patch in first post
Click to expand...
Click to collapse
I tried.
but didnt work either
from which factory image is this patched img?
Which platform tools are u using?
Frost Storm said:
I tried.
but didnt work either
from which factory image is this patched img?
Click to expand...
Click to collapse
The latest global
jaythenut said:
The latest global
Click to expand...
Click to collapse
Nope It still says
Code:
< waiting for device >
...
OKAY [ 0.058s]
finished. total time: 0.059s
PS M:\Pixel_5\platform-tools_r30.0.4-windows\platform-tools> fastboot flash boot magisk_patched.img
target reported max download size of 268435456 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.740s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.821s
Frost Storm said:
Nope It still says
Code:
< waiting for device >
...
OKAY [ 0.058s]
finished. total time: 0.059s
PS M:\Pixel_5\platform-tools_r30.0.4-windows\platform-tools> fastboot flash boot magisk_patched.img
target reported max download size of 268435456 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.740s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.821s
Click to expand...
Click to collapse
Ok have you put the patch in the fastboot folder and done
Fastboot flash boot magisk_patched.img
jaythenut said:
Ok have you put the patch in the fastboot folder and done
Fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Correct
Before I inlocked the bootloader successfully
Frost Storm said:
Correct
Before I inlocked the bootloader successfully
Click to expand...
Click to collapse
Did you turn on usb debugging and put the phone into bootloader mode
jaythenut said:
Did you turn on usb debugging and put the phone into bootloader mode
Click to expand...
Click to collapse
Thats funny
yes, I did, although this is not mentioned in most guides
Frost Storm said:
Thats funny
yes, I did
Click to expand...
Click to collapse
Well I'm out of ideas sorry couldn't help
jaythenut said:
Well I'm out of ideas sorry couldn't help
Click to expand...
Click to collapse
Same for me
This not my first time (had Nexus 4, 5, 6P and Pixel 2 XL all with root from day one)