Wrote down guide how to get STOCK version of Android for XT1572 - Moto X STYLE, and also install TWRP recovery and get root with xposed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Last UPDATE: 25/02/2017
1. GUIDE TO STOCK
@Prazaar 's provided link with STOCK files.
@lAndroXl guide here (Files also for other versions of device).
@dbolivar guide here for RETLA-DS (Brazil).
Stock 6.0.1 EU here, my mirror here (6.0.1 with security patch from September).
Flash scripts - here, or my script here. (for Windows - flashes STOCK files without re-locking bootloader, but also wipes data)
you need adb/fastboot drivers installed (Good ADB installer for PC can be found here);
you need to backup all your data on your phone, guide will erase everything;
reboot your phone into bootloader mode and plug in your usb cable which is connected to your PC. (power off your device then press the POWER and VOLUME DOWN button for 3-4 seconds);
Open a command prompt in the folder where you unpacked the zip file you downloaded before (press SHIFT + RIGHT CLICK on a empty space then "open command prompt here");
Check the functionality of the adb drivers, simply type "fastboot devices" and you will see a list with your connected devices in bootloader mode.
Type every single command in the command prompt window from the list below. (You can ignore OEM LOCK commands if you not wish to lock down bootloader, but just update device to latest version of Android!);
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
[INDENT](for [B]5.1.1 [/B]there are one more file)
fastboot flash system system.img_sparsechunk.9[/INDENT]
[INDENT](for [B]6.0.1[/B] there are more files)
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11[/INDENT]
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
2. UNLOCK BOORLOADER.
Remember, that after unlocking bootloader, all device will be WIPED.
Code:
fastboot oem unlock UNIQUE_KEY
3. FLASH TWRP RECOVERY.
twrp-3.0.2-0-clark.img from here.
Code:
fastboot flash recovery twrp-3.0.2-0-clark.img
Note: After flashing TWRP, boot into custom recovery and make restart to recovery again!
4. INSTALL SUPERSU.
Flash 2.62-3 from TWRP from here. (Later from Play Store upgrade to latest version);
OR
Flash latest SuperSU root ZIP from here.
(before flashing this, TWRP-Advanced-Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and then flash ZIP file.)
5. INSTALL XPOSED.
Latest v86 from here. (xposed-v86-sdk23-arm64.zip)
OR
Latest unofficial SYSTEMLESS Xposed from here. (You need 2.76+ SYSTEMLESS root, latest MAGISK Iterface from here and Material Design Xposed Installer to work)
6. To make OTA update.
Remove XPOSED (can be turned off from XPOSED app) + UNROOT (can be done from SUPERSU app) + remove MAGISK (use latest unintaller from thread);
Flash STOCK recovery file from FASTBOOT (fastboot flash recovery recovery.img);
Now you can perform OTA update;
Follow all steps from guide (I do - > TWRP, SYSTEMLESS ROOT, MAGISK, XPOSED).
I have a Brazilian xt1572 with marshmallow via OTA. Do you think this method will work for me? I mean, without flashing the 6.0 firmware first?
Enviado de meu XT1572 usando Tapatalk
But if you make TWRP read only, how can you flash SuperSu and Xposed Framework?
Inviato dal mio XT1572 utilizzando Tapatalk
bbb77 said:
But if you make TWRP read only, how can you flash SuperSu and Xposed Framework?
Inviato dal mio XT1572 utilizzando Tapatalk
Click to expand...
Click to collapse
yea, you right, I forgot. will edit.
After checking if my device boot up, I restarted to twrp recovery, and unchecked read only. Thanks!
danielgava said:
I have a Brazilian xt1572 with marshmallow via OTA. Do you think this method will work for me? I mean, without flashing the 6.0 firmware first?
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
Its hard to tell that. After upgrading mine stock 5.1.1 to 6.0 via OTA, I unlocked bootloader, but didnt do device restart and did flash TWRP, after that mine device got bootloop. If you are ready to experiment, you can try, but remember that you will wipe all your data on internal storage. Its strange why now I can boot up my device, I think that restart of device after unlocking bootloader and restart after booting into twrp (read only), could change something.
I'll give it a try later, but for insurance, do you have the link for the Brazilian 6.0 firmware?
Never mind, I've found it: https://mega.nz/#!9ItwmIKb!-73GF5Sk00BpkDeFWIJzcUAp2hOFIZS7ksJ5al0CgiA
Enviado de meu XT1572 usando Tapatalk
danielgava said:
I'll give it a try later, but for insurance, do you have the link for the Brazilian 6.0 firmware?
Never mind, I've found it: https://mega.nz/#!9ItwmIKb!-73GF5Sk00BpkDeFWIJzcUAp2hOFIZS7ksJ5al0CgiA
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
Ok, good luck!
What about Indian XT1572?
Can anyone confirm this for India? Or should I risk being the first one to try it on an Indian XT1572 Dual Sim? Although I'll have to wait for a week. My phone is at the service center currently. It apparently had a manufacturing defect in the audio jack.
Any XT1575 owners doing this with success?
radpp16 said:
Any XT1575 owners doing this with success?
Click to expand...
Click to collapse
XT1575 US here. This worked for me on the second try. I followed the procedure in the OP with the following exceptions. Never unchecked system read only in step 3, and never installed xposed. I used the systemless supersu version referenced in the OP and I'm rooted. Confirmed with a few apps that require root like LMT Pie.
The first time I tried this I fastboot flashed, booted straight into recovery, kept system read only, rebooted to recovery, then rebooted into the ROM before I made any changes. I just wanted to be extra sure everything was ok. When I tried to reboot to recovery I got the "no command" error with the android laying on his back. Rooting, even if it is systemless seems to be necessary before you reboot into the system to make TWRP stick.
jason2678 said:
XT1575 US here. This worked for me on the second try. I followed the procedure in the OP with the following exceptions. Never unchecked system read only in step 3, and never installed xposed. I used the systemless supersu version referenced in the OP and I'm rooted. Confirmed with a few apps that require root like LMT Pie.
The first time I tried this I fastboot flashed, booted straight into recovery, kept system read only, rebooted to recovery, then rebooted into the ROM before I made any changes. I just wanted to be extra sure everything was ok. When I tried to reboot to recovery I got the "no command" error with the android laying on his back. Rooting, even if it is systemless seems to be necessary before you reboot into the system to make TWRP stick.
Click to expand...
Click to collapse
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)
Enviado de meu XT1572 usando Tapatalk
danielgava said:
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
I will appreciate if you could explain how did you install SuperSu via fastboot?
Thanks!
For "TWRP - read only" I can refer to SuperSu thread:
"If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!"
sayV said:
Can anyone confirm this for India? Or should I risk being the first one to try it on an Indian XT1572 Dual Sim? Although I'll have to wait for a week. My phone is at the service center currently. It apparently had a manufacturing defect in the audio jack.
Click to expand...
Click to collapse
all is good.. @freakzapster has already done this aanndd it works fine
BooBzi said:
I will appreciate if you could explain how did you install SuperSu via fastboot?
Thanks!
For "TWRP - read only" I can refer to SuperSu thread:
"If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!"
Click to expand...
Click to collapse
Sorry I meant via ADB. Here is the link:
http://forum.xda-developers.com/showthread.php?p=64055153
Enviado de meu XT1572 usando Tapatalk
danielgava said:
Sorry I meant via ADB. Here is the link:
http://forum.xda-developers.com/showthread.php?p=64055153
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
Ok, thanks! That make sense now.
I have an Australian xt1752 Moto X style and i tried the trupure MM rom.
my steps were:
unlock
install TWRP
backup the entire phone , all of it to external card and then save the backup to pc just in case
wipe all partitions except for internal and ext card
flash the trupure mm rom already rooted and ready for exposed.
clear cache
boot
problem is i dont have wifi working and if i flash the modem either from the eu 5.1.1 or the us or the indian version my wifi works but then the sim card stops being detected and no calling or sms working.
what i didnt try is flashing one of these modems and then restoring my efs partition from the backup of twrp.
Other then this the phone is much much faster especially for gaming.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
jason2678 said:
XT1575 US here. This worked for me on the second try. I followed the procedure in the OP with the following exceptions. Never unchecked system read only in step 3, and never installed xposed. I used the systemless supersu version referenced in the OP and I'm rooted. Confirmed with a few apps that require root like LMT Pie.
The first time I tried this I fastboot flashed, booted straight into recovery, kept system read only, rebooted to recovery, then rebooted into the ROM before I made any changes. I just wanted to be extra sure everything was ok. When I tried to reboot to recovery I got the "no command" error with the android laying on his back. Rooting, even if it is systemless seems to be necessary before you reboot into the system to make TWRP stick.
Click to expand...
Click to collapse
i had the android laying on his back with no command screen in recovery once aswell, what i did was while at that screen i press power + up for 3 second and release up and then its taken to the default recovery menu
Alanbarnes said:
I have an Australian xt1752 Moto X style and i tried the trupure MM rom.
my steps were:
unlock
install TWRP
backup the entire phone , all of it to external card and then save the backup to pc just in case
wipe all partitions except for internal and ext card
flash the trupure mm rom already rooted and ready for exposed.
clear cache
boot
problem is i dont have wifi working and if i flash the modem either from the eu 5.1.1 or the us or the indian version my wifi works but then the sim card stops being detected and no calling or sms working.
what i didnt try is flashing one of these modems and then restoring my efs partition from the backup of twrp.
Other then this the phone is much much faster especially for gaming.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
i had the android laying on his back with no command screen in recovery once aswell, what i did was while at that screen i press power + up for 3 second and release up and then its taken to the default recovery menu
Click to expand...
Click to collapse
For wifi you can flash TruPureXMM modem!
BooBzi said:
For wifi you can flash TruPureXMM modem!
Click to expand...
Click to collapse
I just tried that and WiFi now works but now I have no network signal. I tried redoing it same thing. I also restored my efs but nope now no phone network
Alanbarnes said:
I just tried that and WiFi now works but now I have no network signal. I tried redoing it same thing. I also restored my efs but nope now no phone network
Click to expand...
Click to collapse
Clean wipe, flash ROM, flash modem?
I did almost the same but I skip " changed to read only, and reboot to recovery again, so it sticks on. Reboot device normally, see that it boots normal. After that, I boot to TWRP again, uncheck read only on mount menu."
After instalation SU and xspoed in twrp reboot system i got loop x2 or x3 but after that system loaded
android starts up
optimalization apps xx/175 :_)
Related
SOAK4 UPDATED + ROOT + DOWNGRADE
PS1: TESTED ON XT1225 BR RETAIL and TIMBR.
New GDRIVE mirrors = https://goo.gl/o3TvVz
1st OPTION:
1. Make sure you are / Install 5.0.2 (22.33/34.16) BR RETAIL or TIMBR (if you're, jump to step2)
a. Download the correct ROM zip with flash.bat commands: ( https://goo.gl/Nq69AU)
b.1. Install this zip file with RSDLite. Steps: (http://forum.xda-developers.com/droi...mware-t3074724)
or
b.2. Install thru ADB/Mfastboot
-Extract downloaded zip file to any folder in your PC, run Command Prompt from inside that folder (FILE/RUN COMMAND PROMPT). Plug your device in fastboot/bootloader mode and type "FLASH.BAT" without quotes.
or
b.3. Restore TWRP backup (you need to install TWRP 3.0.2.0 modded inside backup zip = https://goo.gl/lcE5mo)
-see steps 04-10 from 2nd OPTION using above zip.
2. Make sure if you are in the correct version, Config/About (5.0.2-LXG22.33/34-12.16 RetailBR or TIMBR)
3. Download the OTA/SOAK1 (https://goo.gl/gdOsWW)
4. If you have a locked bootloader, enable "OEM unlock" on "Developers Options" just in case...
5. Put this last zip file in /sdcard/ (root) PS: Do not extract or rename the file (Blur_Version.24.61.61.quark_retbr.retbr.en.BR.zip )
6. Go Config/About/Update and follow the steps for update.
*PS: If it doesn't recognize as new update, you can try flashing in stock recovery.
7. After soak1 upgrade finishes, download soak2 (https://goo.gl/aGMnAk) and repeat steps 4 and 5 with the new files.
*PS: Idem above
8. After soak2 upgrade finishes, download soak3 (https://goo.gl/NZ1TkF) and repeat steps 4 and 5 with the new file.
*PS: Idem above
9. After soak3 upgrade finishes, download soak4 (https://goo.gl/7ctoFV) and repeat steps 4 and 5 with the new file.
*PS: Idem above
2nd OPTION:
1. You can be in any ROM (KK, LP, CM, RR etc)
2. Download my Backup from SOAK for TWRP (choose one):
-SOAK 4 = https://goo.gl/PVJp9t
-SOAK 3 = https://goo.gl/zH5BTl
-SOAK 2 = https://goo.gl/URsYqT
-SOAK 1 = https://goo.gl/5wC5Cd
3. Download and extract the ADB PACK.zip for any folder in your PC (https://goo.gl/WjcqpB)
4. Make sure if your bootloader is unlocked to be able to install TWRP.
5. Run Command Prompt from inside this folder (second zip) (FILE/RUN COMMAND PROMPT). Plug your device in fastboot/bootloader mode and type "mfastboot flash recovery twrp3020m.img" without quotes
6. Still in bootloader, enter RECOVERY MODE and start TWRP
7. Select Restore and make a backup for SYSTEM/DATA/BOOT/MODEM/RECOVERY/LOGO
8. Keep TWRP opened and your phone plugged, extract ZIP from item 2 aside your new backup
/sdcard/TWRP/BACKUPS/*yourserialnumber/
9. In twrp, select WIPE / ADVANCED e erase: DALVIK/SYSTEM/CACHE/*DATA
* If your were in stock rom, you can try to keep your apps, but I do not recommend.
10. Go RESTORE in TWRP and restore
for SOAK4= "6.0.1-Soak4-24.66.2"(boot/system/modem/recovery*)
for SOAK3= "6.0.1-Soak3-24.66.1" (boot/system/modem/recovery*)
for SOAK2= "6.0.1-Soak2-24.61.68" (boot/system/modem/recovery*)
for SOAK1= "6.0.1-Soak1-24.61.61" (boot/system/modem/recovery*)
*Do not select RECOVERY if you want to keep TWRP
11. ON TWRP main menu, choose REBOOT SYSTEM
3rd OPTION
1. Download and extract the 24.66.2 fastboot zip file: https://goo.gl/D6dHzD
2. Run Command Prompt inside that folder (FILE / RUN CMD)
3. You don't need a unlocked bootloader, but it's highly recommended. If you have a locked bootloader, at least enable "OEM unlock" on "Developers Options" just in case...
4. Plug your maxx in fastboot/bootloader mode, type in prompt: "0FLASH601.bat" without quotes.
PS2: Commands inside FLASH502.BAT item b.2. from 1st OPTION:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash radio radio.img
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
ROOT for 6.0.1 SOAK
1. Download especific supersu version: (https://goo.gl/ejEZfY)
2. Put the file on your internal memory.
3. Install TWRP (Steps 3 to 6 , 2nd OPTION)
4. Install downloaded file in TWRP
PS3: If your device is booting on fastboot when turning on, you need to download ADB PACK and run this command: mfastboot OEM FB_mode_clear
PS4: Sorry for my bad english.
works fine!
thank you!
Fine
Moderator Edit:
@neo910 It is not good practice, or necessary, to quote the whole OP. It can cause issues with page loading time for those on limited bandwidth connections or when mobile.
Great at least.
Thanks
I'm always facing constant crashes of the same applications.
Google Play Books
Google Play Services
Both appear, "Application X stop working".
----
Estou enfrentando constantes crashes sempre dos mesmos aplicativos.
Google Play Books
Google Play Services
Ambos aparecem, "Aplicativo X parou de funcionar".
What if I'm on stock brazilian 5.0.2, never rooted or unlockd my bl? Can I flash this via stock recovery?
kamikass said:
What if I'm on stock brazilian 5.0.2, never rooted or unlockd my bl? Can I flash this via stock recovery?
Click to expand...
Click to collapse
Yes.
Is there any way to return to stock 5.0.2, for example with a TWRP backup?
daldegam said:
I'm always facing constant crashes of the same applications.
Google Play Books
Google Play Services
Both appear, "Application X stop working".
----
Estou enfrentando constantes crashes sempre dos mesmos aplicativos.
Google Play Books
Google Play Services
Ambos aparecem, "Aplicativo X parou de funcionar".
Click to expand...
Click to collapse
You can uninstall updates for this apps and re update from google play.
To uninstall updades, just go config/apps, select The APP, go for The '3dots' menu and uninstall any update.
kamikass said:
What if I'm on stock brazilian 5.0.2, never rooted or unlockd my bl? Can I flash this via stock recovery?
Click to expand...
Click to collapse
Yes, u can, but just with steps from first option.
nachoserrano20 said:
Is there any way to return to stock 5.0.2, for example with a TWRP backup?
Click to expand...
Click to collapse
Yeap, you can, just make a backup of your stock 5 before go to 6.0.
If you get WiFi/signal problems, just flash radio.img (steps on 2nd option)
Can't install on Chilean Moto Maxx
Apparently it only works with brazilian retail moto maxx, not with anothers... Back to chilean stock
nachoserrano20 said:
Apparently it only works with brazilian retail moto maxx, not with anothers... Back to chilean stock
Click to expand...
Click to collapse
If you unlock your bootloader you can flash retail brazil - my phone is from puerto rico.
nachoserrano20 said:
Apparently it only works with brazilian retail moto maxx, not with anothers... Back to chilean stock
Click to expand...
Click to collapse
I have moto turbo ( xt 1225 india) with unlocked boot loader, worked for me.
Do not work Droid Turbo BootLoader unlock! =(
I'm chilean
nachoserrano20 said:
Apparently it only works with brazilian retail moto maxx, not with anothers... Back to chilean stock
Click to expand...
Click to collapse
Yes you can.
100% working
Great
---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------
Steve-x said:
If you unlock your bootloader you can flash retail brazil - my phone is from puerto rico.
Click to expand...
Click to collapse
Always you unlock bootloader or result error.
Yes, is 100% functional.
I never use the firmware from my region, I bored to stay.
junior_ilha said:
If you get WiFi/signal problems, just flash radio.img (steps on 2nd option)
Click to expand...
Click to collapse
The problem is with signal - it is much more lower then on 5.0.2 brazil and switching 4g-3g very often, so it takes a lot power from battery, even more then a screen in a day.
5.0.2 modem is not working on 6.0.1
junior_ilha said:
Yes, u can, but just with steps from first option.
Click to expand...
Click to collapse
Didn't have to make any changes to flash.bat, I simply dirty flashed it over 5.0.2 and now I'm running 6.0.1 flawlessly...
kamikass said:
Didn't have to make any changes to flash.bat, I simply dirty flashed it over 5.0.2 and now I'm running 6.0.1 flawlessly...
Click to expand...
Click to collapse
Glad to hear it.
kamikass said:
Didn't have to make any changes to flash.bat, I simply dirty flashed it over 5.0.2 and now I'm running 6.0.1 flawlessly...
Click to expand...
Click to collapse
How did you do it?, i've got stock 5.0.2 rooted, twrp3 installed, and unlocked bootloader, so i just download ota/zip from step 3 and do what?
I don't have a computer near, so i can't fastboot anything. Wonder if i can flash the ota/zip just with my phone only...
Thanks im advance
Enviado desde mi XT1225 mediante Tapatalk
Anhell said:
How did you do it?, i've got stock 5.0.2 rooted, twrp3 installed, and unlocked bootloader, so i just download ota/zip from step 3 and do what?
I don't have a computer near, so i can't fastboot anything. Wonder if i can flash the ota/zip just with my phone only...
Thanks im advance
Enviado desde mi XT1225 mediante Tapatalk
Click to expand...
Click to collapse
I was on stock unrooted and locked bl 5.0.2 brazilian firmware, so my case was different...
In your case, i'd suggest you to follow instructions on the OP...
Anhell said:
How did you do it?, i've got stock 5.0.2 rooted, twrp3 installed, and unlocked bootloader, so i just download ota/zip from step 3 and do what?
I don't have a computer near, so i can't fastboot anything. Wonder if i can flash the ota/zip just with my phone only...
Thanks im advance
Enviado desde mi XT1225 mediante Tapatalk
Click to expand...
Click to collapse
You are in half way, just restore 6.0.1 twrp backup, but you will need to flash modem601.img after. Maybe you can do it with ROM manager or similar APP.
Flashed and got bootloop. What can I do?
i rooted my deviced. Used systemless root. in the hope OTA would work when a update arrived.
Now there is a update but.... it says the update fails. (in dutch).
I used supersu unroot, but it still says update failed.
I tried using the MDM tools as here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/91996
... but that is giving a bogus cannot connect to internet message (I think it just means that there is no server for the g4 phone, internet is fine and fast on phone and pc)
I want the update but Now i am stuck:
-I do not want to re-lock the phone
-I do want the update. (euret -> may to juli security update)
Questions:
-Are there any meaning full error messages.. anywhere?
-are there other ways to flash the OTA?
-I see flashing stock should work. But is my unrooted rom different from stock?
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
Edit: and maybe logo.bin when you had removed the unlocked warning
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
downloading XT1642_ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip now.
is only option anyway because after trying to flash supersu it won't boot anyway. (but still boots into fastboot mode.. no brick yet)
thx
have you used xposed? or custom kernel?
Bender1987 said:
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Click to expand...
Click to collapse
Thank you for this information Bender. I was wondering the exact same thing. I am rooted on a Moto G4 and i was wondering if a OTA update, or reflashing stock would wipe my data + all installed apps.
If i do it your way it shouldn't be any concerns?
srgudhka said:
have you used xposed? or custom kernel?
Click to expand...
Click to collapse
no only supersu and modified hosts file with adaway (main reason for root is titanium backup)
flashed boot, recovery and system with
Code:
fastboot oem fb_mode_set
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
system boots now with all user data intact in may 2016 update.
However system update nows says it is up to date. .... maybe they retracted the update temporary? ... patience.... (reteu).
@leuk_he
I have a RETEU version here in germany and download the XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip file, which had the same build no as my g4+.
If you try to flash files from the wrong rom, you get an error while flashing or lost temporary your WiFi and IMEI till you find and flash the right one.
So compare the build no on your phone and the stock rom file.
@Zajbot
As long as you don't wipe cache or data or use fastboot erase userdata, all your data should be there.
I have done the same yesterday and all data is still on my phone
---------- Post added at 13:16 ---------- Previous post was at 13:11 ----------
You don't need the OEM fb_mode_set.
Try it again in few hours or reboot, the update should pop-up again, don't worry.
Wifi and imei info are correct(NL) I checked the XT1642_ATHENE from the bootloader screen (did not know this number)
but... patience is a hard one.... :crying::crying: ... and if people say "don't worry... i worry..." bad habit.
Build number accorindg to phoneinfo is MPJ24.139-48 ... but i think that is what i just flashed. Not sure if that is what was in the phone before.
i added the oemset becuase it cried about wrong signature on boot.img it still did afterwards.
@leuk_he
Then you have maybe the wrong ROM. I flashed boot recovery and system and had no errors. But my build no. matches before the update.
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
How does the sideload works?
Thanks
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Bender1987 said:
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Click to expand...
Click to collapse
Didn't work for me. I get the bootloadermenu and when I switched to RECOVERY I got the ANDROID-Picture with "No Command".
Flashing a new recovery.img don't change anything.
Is a sideload flah with adb possible?
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Bender1987 said:
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Click to expand...
Click to collapse
I think there is a problem with my recovery. I flashed the recovery from rom-zip
Edit: get the recovery
Edit 2.: Give up, get with my and yours OTA.zip a sideload mistake (number 7). Now I wait for the next OTA, next days will be hard without ROOT
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Bender1987 said:
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Click to expand...
Click to collapse
thanks for your hint, I start it tomorrow, have a good night
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
SoNic67 said:
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
Click to expand...
Click to collapse
I haven't flash the TWRP, I always boot by mfastboot to TWRP
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
Tried sideloading with twrp , but it gave error 7 on build number. "this device has . "
thx anyway for sharing.
I will now try load older system images with older build number.
/edit:
Flashed MJP-..23 like bender and it now says a update is availble.
interesting side note. when using the build-48 it already showed battery indicator on motowake screen but still at may-2016 security update.
Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)
Firmwares
the latest firmware as of time of writing is February's 2020 OTA (BECKHAM_RETAIL_9.0_PPWS29.131-27-1-18_subsidy-DEFAULT_regulatory-DEFAULT_CFC) = https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
previous OTAs RETAIL variant can be found here = https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
future OTAs possibly here = https://androidfilehost.com/?w=search&s=beckham
other variants = https://mirrors.lolinet.com/firmware/moto/beckham/official/
Unlock Bootloader
first you need to install Motorola Drivers = https://support.motorola.com/us/en/solution/MS88481
- ATTENTION - use the most up-to-date ADB Drivers otherwise will brick if older version is used; instead of downloading ADB elsewhere which is often old version, get it directly from GOOGLE, here = https://dl.google.com/android/repository/platform-tools-latest-windows.zip
now you can proceed to unlock bootloader = https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
TWRP
get the official TWRP here = https://dl.twrp.me/beckham/
- ATTENTION - if you just want root access, then there's no need to install TWRP, just boot from the .img once using the latest version
use TWRP to make a backup of EFS partition before installing anything, store the backup files outside of the device
if you want custom ROMs or GSI, then you will need to install TWRP installer .zip into the recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the latest .zip version in the recovery partition. Unfortunately the only official installable version of TWRP that exists is bugged, and the TWRP developers haven't fixed it yet, go talk to them ask for some love, be respectful = https://github.com/TeamWin/android_device_motorola_beckham/issues
Magisk
install Magisk using the new&correct method AKA "Boot Image Patching Method" to be able to install OTA later = https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
when OTA arrives, you may manually install it whilst retaining Magisk by carefully following these instructions = https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
- ATTENTION - you won't be able to install stock OTAs if you use older method or if system partition is modified, be really careful to not alter the hash of the partitions
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
@heynando, what is the difference between "retail" and "retus"? Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
ritchea said:
@heynando, what is the difference between "retail" and "retus"?
Click to expand...
Click to collapse
RETUS is short for Retail + US.
The difference between RETUS and RETAIL is, I imagine, cannot confirm, the same RETAIL firmware with some US regional modifications such as bloatware or CSC thing
you can check which model is yours in SETTINGS > SYSTEM > ABOUT PHONE > SOFTWARE CHANNEL. Or in the bootloader by running the command
Code:
fastboot getvar product
you can find the entire list of product codes here = https://mirrors.lolinet.com/firmware/moto/readme-en.html#listone
XT1929-4(Canada, SS, 4+32GB) XT1929-3(NA/Sprint, SS, 4+32GB)
XT1929-4(NA/AMZ/BWACA/RETCA/RETUS/USC, SS, 4+64GB)
XT1929-5(BRAZIL/RETBR/TIMBR/TEFBR, DS, 4+64GB / 6+128GB)
XT1929-6(LATAM/AMXLA/NIIPE/ATTMX//TEFCL/TEFPE/RETLA/RETAR/RETMX/RETCL/AMXMX, DS, 4+64GB)
XT1929-6(LATAM/RETLA/TEFCO/TIGCO, DS, 6+128GB)
XT1929-8(EMEA_APAC/RETEU/DTEU, DS, 4+32GB / 4+64GB)
ritchea said:
Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
Click to expand...
Click to collapse
I believe that's the internal version of the software. If the number changes that emphasizes there has been software changes and/or tweaks in the system and/or firmware. If the number doesn't change, then it's just a regular security patch with no further modifications in system and/or firmware.
Thanks for that info. Yeah, I know mine has the retus software channel. I just couldn't find or figure out if Retail was actually one word or if it was a combo of ret+ail. That version has a LOT of software posted.
I flashed retail on an EU model. And after it the software channel say Reteu just like the original. Also the model number is as it should be. In my opinion you can flash retail firmware on us and EU models.
confirmed that this firmware is working on XT1929-4
these are the steps I took:
downloads and setup
install moto drivers (in windows, not needed for linux)
install android tools (adb and fastboot)
downloaded official TWRP
downlaoded and extracted the firmware
backup of partitions (including efs)
Code:
adb reboot bootloader
fastboot boot twrp_recovery.img
backed up lots of partitions
rebooted system
copied the TWRP backup files to my pc for safe keeping
set the fastboot slot (i did this because many of teh fastboot commands below were failing)
Code:
adb reboot bootloader
fastboot --set-active=a
rebooted back into bootloader
installed the firmware
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot reboot
installed magisk the new good way
did the initial device setup
installed magisk manager
copied the boot.img from the extracted firmware above to the phone.
followed these steps for boot img patching and install of magisk https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
sirkuttin,
Thanks for the detail how to. That worked perfectly for me, and my moto z3 play, same model as yours. I could not get the ota or even lenovo smart assistant to work on my phone. It basically had it locked up, stuck on the boot logo. I'm assuming its the old way of install magisk that caused that. This got me on the latest firmware release, and then installed magisk the new way. Lenovo smart assistant was useful in downloading the firmware.
Thanks.
Hi I tried the new magisk install way. I'm on XT1929-4_BECKHAM_RETUS_9.0_PPW29.183-29-1, copy boot.img and patched it to magisk_patched.img. Then after fastboot flash boot /path/to/magisk_patched.img and a reboot, i'm not stuck on the motorola powered by android screen. Verity mode is set to disabled.
I tried holding down the power button to simulate a battery pull but no luck, the screen just stays on. Can anybody give me any advise? I think now I have to just wait till the device is out of juice. Never experience this before.
---------- Post added at 02:16 PM ---------- Previous post was at 01:31 PM ----------
So the battery pull is "Power + Vol Down". I was able to flash the PPW29.183-29-1 firmware and get it going again. I noticed it tried to upgrade me to PPW29.183-29-1-2 so I must have been on newer firmware. I flashed the magisk_patched and am rooted now.
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
ch3mn3y said:
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
Click to expand...
Click to collapse
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
heynando said:
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
Click to expand...
Click to collapse
It, unfortunately, does... However I csnnot update (continous update unsuccesful) :f Have to check if Xposed module is not a reason.
And You probably could use Installer to flash stock recovery? If not TWTP itself however I've never checked if one for Play has access to recovery partiotion to flash images. It should gave if it can be done using the installer...
Sent from my Moto Z3 Play using Tapatalk
ch3mn3y said:
However I csnnot update (continous update unsuccesful)
Click to expand...
Click to collapse
Me too and it drove me nuts, I did patch the /boot partition with the original file, but the OTA app still failed to install, even after reboot. And there's no useful data in the logcat to debug the app. So I gave up and had to use Titanium to freeze the OTA app otherwise it would keep trying to download and install infinitely.
ch3mn3y said:
:f Have to check if Xposed module is not a reason.
Click to expand...
Click to collapse
It's probably not because I don't use it and the OTA method didn't work me either
ch3mn3y said:
And You probably could use Installer to flash stock recovery?
Click to expand...
Click to collapse
Yes you're right, I agree there..
heynando said:
Yes you're right, I agree there..
Click to expand...
Click to collapse
Just checked the inside of the installer zip file and it won't work. Still once every 3 months it wouldn't be a problem to connect device to PC and flash recovery.img with fastboot.
Is there a list with a commands and order how to flash Z3 Play images of official firmware? I want July patches and have some problems, so clean reflash is what I need.
Additional question is if I have to use "-u" when flashing second and other system images? Remember I had to do it with my X Play coz of unlocked bootloader and here I have one in the same state as well. If yes than could someone tell me where to put it, coz I'm not sure...
tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Ramble2k said:
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Click to expand...
Click to collapse
This one, make sure to get the latest. https://mirrors.lolinet.com/firmware/moto/beckham/official/RETUS/
Hi, I'm trying to unlock my Moto Z3 Play bootloader, but I don't get the code on CMD, but only a few numbers ... The version of my device is PPW29.131-27-1-11, channel RETBR software.
Someone went through this, can you tell how to reverse this situation?
I couldn't get the bootloader unlocked for xt1929-4. I tried different computers, Linux and win. Have latest adb and fastboot. When fastboot OEM get_unlock_data is given, I says counttas slot not found etc., can someone help?
It may seem obvious, but you
checked OEM unlocking and USB Debugging?
NEED HELP
1. I wiped my system .. no system to load into
2. MIFLASH giving antirollback check error for all Fastboot roms
3. TWRP wont allow me to flash roms and there are no roms copied in the phone. getting error while copying files to the phone via TWRP
any solution ..
other than removing antirollback check in the roms .. ?
1. Is your bootlader CURRENTLY unlocked?
2. Which TWRP did you use?
3. Did you format all data using TWRP (enter yes to confirm) AND reboot TWRP before trying to copy rom to phone?
Sent from my Mi 10 Pro using Tapatalk
ted presley said:
1. Is your bootlader CURRENTLY unlocked?
2. Which TWRP did you use?
3. Did you format all data using TWRP (enter yes to confirm) AND reboot TWRP before trying to copy rom to phone?
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
bootload is unlocked
I figured it out loaded mi recovery wiped data and entered the system ..
I want to go to flash eu rom
do i dirty flash or do i clean flash the rom
stuck up on that part
TED can u help plz ..
I have used twrp-cmi-3.3.1-1
twrp-umi-3.3.1-2
what twrp are u using and i havent installed twrp
i am just booting TWRP
could you please tell me steps to 20.4.27
It seems you still on stock mi flash recovery, if your bootloader currently still unlocked.
You have to:
1. Go to fastboot
2. Flash TWRP again
3. Without restaring the device, reboot TWRP by using button combination: power off the device, press and hold volume down button until you see twrp screen
4. Format all data using twrp (option enter yes to confirm)
5. Reboot recovery using option reboot in TWRP recovery
6. Plug in pc to copy rom and flash.
Sent from my Mi 10 Pro using Tapatalk
ted presley said:
It seems you still on stock mi flash recovery, if your bootloader currently still unlocked.
You have to:
1. Go to fastboot
2. Flash TWRP again
3. Without restaring the device, reboot TWRP by using button combination: power off the device, press and hold volume down button until you see twrp screen
4. Format all data using twrp (option enter yes to confirm)
5. Reboot recovery using option reboot in TWRP recovery
6. Plug in pc to copy rom and flash.
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
twrp gives error saying
failed to mount /system_root permission denied
failed to mount /vendor permission denied
is it necessary the twrp should be installed
is it possible to just boot twrp while loading zips ..
thanks
sanish4u said:
twrp gives error saying
failed to mount /system_root permission denied
failed to mount /vendor permission denied
is it necessary the twrp should be installed
is it possible to just boot twrp while loading zips ..
thanks
Click to expand...
Click to collapse
problems just increasing now ..
the phone wont boot to twrp it will just go to fastboot
twrp wont load through volume down and power button
Seems like you lost TWRP
Reinstall twrp
Code:
Fastboot flash recovery twrp.img (use your filename)
Fastboot reboot recovery
Then when your in click the top right icon which says wipe. Here click on the right button I forget what it says I think it says wipe data. Next screen will ask you to type out the word "yes" you have to do this. You will lose all your data on the phone.
Now provided you have the drivers correctly installed you should see your phone as accessible from your computer. Paste your rom into the drive from your computer to the phone drive.
Once completed, go back to your phone you should be on the main menu click on top right it should say install. I believe you'll be in root directory you have to navigate to sdcard. Look for sdcard folder.
You should see the Rom you copied over, install it. It should take 5 to 10 minutes. Once complete reboot to system. First but will take some time maybe 5 to 10 minutes let it do it's thing.
Your done. If you want magisk, there are lots of guides here to do that as well
IronSingh said:
Seems like you lost TWRP
Reinstall twrp
Code:
Fastboot flash recovery twrp.img (use your filename)
Fastboot reboot recovery
Then when your in click the top right icon which says wipe. Here click on the right button I forget what it says I think it says wipe data. Next screen will ask you to type out the word "yes" you have to do this. You will lose all your data on the phone.
Now provided you have the drivers correctly installed you should see your phone as accessible from your computer. Paste your rom into the drive from your computer to the phone drive.
Once completed, go back to your phone you should be on the main menu click on top right it should say install. I believe you'll be in root directory you have to navigate to sdcard. Look for sdcard folder.
You should see the Rom you copied over, install it. It should take 5 to 10 minutes. Once complete reboot to system. First but will take some time maybe 5 to 10 minutes let it do it's thing.
Your done. If you want magisk, there are lots of guides here to do that as well
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It just wont let me wipe data says permission denied image attached
and wont let me copy rom as it is connected it MTP mode
sanish4u said:
It just wont let me wipe data says permission denied image attached
and wont let me copy rom as it is connected it MTP mode
Click to expand...
Click to collapse
Mtp is ok no issues. Photo is broken can't see what you posted. Try wipe on the left button. Don't wipe system. Did you have a pin code setup for your phone to get in the phone are you entering this pin code when twrp starts? You should enter this pin/password
IronSingh said:
Mtp is ok no issues. Photo is broken can't see what you posted. Try wipe on the left button. Don't wipe system. Did you have a pin code setup for your phone to get in the phone are you entering this pin code when twrp starts? You should enter this pin/password
Click to expand...
Click to collapse
It wont boot twrp or install twrp ..
twrp wont load whatsoever now ..
my only option is only mflash tool ..
is there any Fastboot rom which wont cause anti rollback error check
If anyone finds any solution will be greatly appreciated ..
Thanks
I'm doubt that you have unlocked Bootloader, that's really a big problem here...
If your bootloader is unlocked, our mentioned steps should work fine.
Did you really unlock bootloader? And didn't locked it again accidentally while using miflash?
Sent from my Mi 10 Pro using Tapatalk
The way you describe your problem it seems you had twrp and you booted into it.
Can you tell me what happens when you run
Fastboot flash recovery twrp.img (use your filename)
IronSingh said:
The way you describe your problem it seems you had twrp and you booted into it.
Can you tell me what happens when you run
Fastboot flash recovery twrp.img (use your filename)
Click to expand...
Click to collapse
1. I have bootloader unlocked via miunlock
2. I had booted into TWRP .. it failed to wipe data many times..
3. I installed TWRP and now it does not allow me to do anything ..
4. Wont go to TWRP wont go to Mi recovery and will just go to fastboot
5. MiFlash wont flash as it has anti rollback check error tried all fastboot roms EU and CN
6. Trying to recover it via MIUI recovery loader but it wont download from servers either ..
<img src="https://i.ibb.co/KNjRdNL/twrp.jpg" alt="twrp" border="0">
https://ibb.co/KNjRdNL this was the error message while wiping data
sanish4u said:
1. I have bootloader unlocked via miunlock
2. I had booted into TWRP .. it failed to wipe data many times..
3. I installed TWRP and now it does not allow me to do anything ..
4. Wont go to TWRP wont go to Mi recovery and will just go to fastboot
5. MiFlash wont flash as it has anti rollback check error tried all fastboot roms EU and CN
6. Trying to recover it via MIUI recovery loader but it wont download from servers either ..
https://ibb.co/KNjRdNL this was the error message while wiping data
Click to expand...
Click to collapse
Try another TWRP
Sent from my Mi 10 Pro using Tapatalk
ted presley said:
Try another TWRP
https://1drv.ms/u/s!Amo9DwwPZk-vg9gNxQ-IcpcHDWTI7A
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
Thanks ted it did solve the problem
thanks for all the support
ted presley said:
Try another TWRP
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
I installed miui 12 with the twrp provided. it booted into the system.
I want to install gapps so it try to go back to twrp by using vloume down and power the phone goes to fastboot.
Volume up and power will load xiaomi recovery v3.0
Volume up and down with power will load MIUI rom recovery
What is going wrong why am i not able to load TWRP now ..
sanish4u said:
I installed miui 12 with the twrp provided. it booted into the system.
I want to install gapps so it try to go back to twrp by using vloume down and power the phone goes to fastboot.
Volume up and power will load xiaomi recovery v3.0
Volume up and down with power will load MIUI rom recovery
What is going wrong why am i not able to load TWRP now ..
Click to expand...
Click to collapse
Unless you use custom MIUI rom, stock MIUI always overwrite TWRP.
BTW, if you flash official China Dev rom, no need to flash GAPPs, just install additional play store apk (plus additional latest play service framework if needed) from apkmirror, all other necessary things installed by Xiaomi already.
Sent from my Mi 10 Pro using Tapatalk
ted presley said:
Try another TWRP
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
thank you brother <3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root & TWRP 3.4.0 for Android 10.
Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html
Installation Instruction
1. Download twrp-3.4.0-0-kane.img and twrp-installer-3.4.0-0-kane.zip TWRP, patched vbmeta.img and Magisk-disable-dm-verity-v20.4.zip (see in the attached files).
2. Copy files:
- twrp-3.4.0-0-kane.img and vbmeta_patch.img to the folder adb with the adb & fastboot drivers;
- twrp-installer-3.4.0-0-kane.zip, Magisk-disable-dm-verity-v20.4.zip on SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash vbmeta C:\adb\vbmeta_patch.img
Code:
fastboot boot C:\adb\twrp-3.4.0-0-kane.img
The phone will load into TWRP.
4. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install twrp-installer-3.4.0-0-kane.zip.
5. Go to "Wipe" and press Format Data for deencryption. Enter Yes on request. We go to TWRP Main Menu and reboot again in Recovery.
6. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install Magisk-disable-dm-verity-v20.4.zip.
7. Reboot into the system.
Has anyone succesfully decrypted data when booting TWRP? I've wiped after installing the ZIP and I cannot decrypt data there. I've tried changing device password from PIN to pass, as it requires me to type a password in TWRP, and I still can't decrypt there.
No problems here.
adb fastboot boot twrp_3.4.0-0.img and then flash twrp_3.4.0-0 zip in TWRP.
Havoc OS booting fine.
Gesendet von meinem Phh-Treble vanilla mit Tapatalk
I think something's messed up with my phone by transitioning from the older TWRP to the newer one
Edit: My device fails to fastboot boot twrp after I try reflashing the entire firmware. I think it has something to do with the edited vbmeta file I was using before, because it boots when I flash the patched vbmeta file this TWRP doesn't need.
ilia3367 said:
After almost a year, the official TWRP for Motorola One Vision has finally arrived!
Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html
Click to expand...
Click to collapse
Good morning,
Currently, I have installed the version you patched, 3.3.1.
Can it be installed from the "unofficial" version: https://forum.xda-developers.com/showthread.php?p=80352223?.
Does it give a problem, or does it work perfectly?
Regards
Enviado desde mi unknown mediante Tapatalk
gonzo1963 said:
Good morning,
Currently, I have installed the version you patched, 3.3.1.
Can it be installed from the "unofficial" version: https://forum.xda-developers.com/showthread.php?p=80352223?.
Does it give a problem, or does it work perfectly?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
The official TWRP instructions do not mention it, but you still need the patched vbmeta file for booting TWRP. Also, encryption is not working as of QSAS30.62-24-10 and 62-24-7 ROMs. I ended up going back to this TWRP version https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839
daekdroom said:
The official TWRP instructions do not mention it, but you still need the patched vbmeta file for booting TWRP. Also, encryption is not working as of QSAS30.62-24-10 and 62-24-7 ROMs. I ended up going back to this TWRP version https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839
Click to expand...
Click to collapse
Good afternoon,
Has anyone tried to install this TWRP starting from a firmware "no touch" ("clean install")?
Regards
daekdroom said:
Has anyone succesfully decrypted data when booting TWRP? I've wiped after installing the ZIP and I cannot decrypt data there. I've tried changing device password from PIN to pass, as it requires me to type a password in TWRP, and I still can't decrypt there.
Click to expand...
Click to collapse
Decryption may or may not work with different OS releases, it's mentioned in TWRP downloads section of this device.
---------- Post added at 07:16 AM ---------- Previous post was at 07:05 AM ----------
gonzo1963 said:
Good afternoon,
Has anyone tried to install this TWRP starting from a firmware "no touch" ("clean install")?
Regards
Click to expand...
Click to collapse
Yes, from what I heard it doesn't boot through fastboot boot either with patched vbmeta or clean ROM. If you are rooted, you can use magisk module TWRP installer, but after flashing you will loose root access asusual or you can flash recovery ramdisk through existing recovery. Also don't forget unofficial builds.
Nevil Sebastian said:
Decryption may or may not work with different OS releases, it's mentioned in TWRP downloads section of this device.
---------- Post added at 07:16 AM ---------- Previous post was at 07:05 AM ----------
Yes, from what I heard it doesn't boot through fastboot boot either with patched vbmeta or clean ROM. If you are rooted, you can use magisk module TWRP installer, but after flashing you will loose root access asusual or you can flash recovery ramdisk through existing recovery. Also don't forget unofficial builds.
Click to expand...
Click to collapse
Good morning,
From what I understand it doesn't work well in either case, does it?.
So what is it for, is it better to use the old "patched" TWRP: https://forum.xda-developers.com/showthread.php?p=82629961?
Regards
Enviado desde mi unknown mediante Tapatalk
gonzo1963 said:
Good morning,
From what I understand it doesn't work well in either case, does it?.
So what is it for, is it better to use the old "patched" TWRP: https://forum.xda-developers.com/showthread.php?p=82629961?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
You can use whichever build you want. We should wait until everything gets solved slowly.
Nevil Sebastian said:
You can use whichever build you want. We should wait until everything gets solved slowly.
Click to expand...
Click to collapse
Good morning,
Thanks for the reply, but ...
This new and official TWRP, does it work 100% or not?
Regards
I did the Instruction to install TWRP and geting Root.
Do I have to unlock my bootloader first before doing this? I just noticed we finally have a custom ROM for the One Vision! This finally makes it worth while to unlock, install TWRP, install a custom ROM and root this thing finally!
alphalog said:
No problems here.
adb fastboot boot twrp_3.4.0-0.img and then flash twrp_3.4.0-0 zip in TWRP.
Havoc OS booting fine.
Gesendet von meinem Phh-Treble vanilla mit Tapatalk
Click to expand...
Click to collapse
[How do you install HavocOS? Is there any ROM source?]
delete this
HourlongTuna5 said:
[How do you install HavocOS? Is there any ROM source?]
Click to expand...
Click to collapse
Havoc-OS GSI
Havoc-OS Generic System Image for all devices
www.pling.com
[email protected]
So which TWRP do you recommend? The latest version (3.4.0-0)? Or the older version (3.3.1-0) ??
tin0o said:
So which TWRP do you recommend? The latest version (3.4.0-0)? Or the older version (3.3.1-0) ??
Click to expand...
Click to collapse
3.4.0-0 (for gsi and stock image)
Download TWRP for kane
Download TWRP Open Recovery for kane
eu.dl.twrp.me
ilia3367 said:
Root & TWRP 3.4.0 for Android 10.
Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html
Installation Instruction
1. Download twrp-3.4.0-0-kane.img and twrp-installer-3.4.0-0-kane.zip TWRP, patched vbmeta.img and Magisk-disable-dm-verity-v20.4.zip (see in the attached files).
2. Copy files:
- twrp-3.4.0-0-kane.img and vbmeta_patch.img to the folder adb with the adb & fastboot drivers;
- twrp-installer-3.4.0-0-kane.zip, Magisk-disable-dm-verity-v20.4.zip on SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash vbmeta C:\adb\vbmeta_patch.img
Code:
fastboot boot C:\adb\twrp-3.4.0-0-kane.img
The phone will load into TWRP.
4. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install twrp-installer-3.4.0-0-kane.zip.
5. Go to "Wipe" and press Format Data for deencryption. Enter Yes on request. We go to TWRP Main Menu and reboot again in Recovery.
6. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install Magisk-disable-dm-verity-v20.4.zip.
7. Reboot into the system.
Click to expand...
Click to collapse
Hi....
Should i use this method for android 11 ?