[Q] Problems while flashing CM, Error while executing updater binary in zip - X Play Q&A, Help & Troubleshooting

Hallo,
i got the new Moto X Play, it should replace my Z1.
Flashing CM is normaly not a real problem for me, but the lux is tricky - i hope you can help me...
adb sideload cm-12.1-20150921-UNOFFICIAL-lux.zip
throws the same error as flashing with TWRP: "E: Error while executing updater binary in zip..."
The TWRP is from here:
http://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
The ROM is from here (SEP21):
http://forum.xda-developers.com/moto-x-play/orig-development/rom-cyanogenmod-moto-x-play-t3205422
The phone is a new XT1562 without provider branding...
Thanks for your help!
untrackable

untrackable said:
Hallo,
i got the new Moto X Play, it should replace my Z1.
Flashing CM is normaly not a real problem for me, but the lux is tricky - i hope you can help me...
adb sideload cm-12.1-20150921-UNOFFICIAL-lux.zip
throws the same error as flashing with TWRP: "E: Error while executing updater binary in zip..."
The TWRP is from here:
http://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
The ROM is from here (SEP21):
http://forum.xda-developers.com/moto-x-play/orig-development/rom-cyanogenmod-moto-x-play-t3205422
The phone is a new XT1562 without provider branding...
Thanks for your help!
untrackable
Click to expand...
Click to collapse
redownload the file

0l1v3rof said:
redownload the file
Click to expand...
Click to collapse
new download, same Problem.
I redownloaded twrp, hasht it, redownloaded and checkt the hash: its the same! i downloaded 2 times the 01.October Build - exactly the same problem.
Any Ideas?

untrackable said:
new download, same Problem.
I redownloaded twrp, hasht it, redownloaded and checkt the hash: its the same! i downloaded 2 times the 01.October Build - exactly the same problem.
Any Ideas?
Click to expand...
Click to collapse
You must download and flash the "twrp-lux-2.8.7-v2.img" , the first version has that bug!

eskamhl said:
You must download and flash the "twrp-lux-2.8.7-v2.img" , the first version has that bug!
Click to expand...
Click to collapse
i already used that image (sha256):
af37b348fca9ac1495b159dc586324c5f53acd1609a17556beca351a53a04201 twrp-lux-2.8.7-v2.img
181df3db9a1d629eef6f46bf5892eb231afec12e6612285cfa931815481adef4 cm-12.1-20151001-UNOFFICIAL-lux.zip
Infos of the phone:
(bootloader) product: lux
(bootloader) board: lux
(bootloader) hwrev: 0x82C0
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Samsung REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8939
(bootloader) mot_sst: 3
(bootloader) max-download-size: 268435456
(bootloader) sku: XT1562
(bootloader) current-time: "Fri Oct 2 13:36:12 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:5.1.1/LPD23
(bootloader) ro.build.fingerprint[1]: .118-10/15:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.21.10.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU

*push* i tried it again, no chance...
any tips?

make a backup first from twrp recovery
then flash CM

With the new Version the problems are fixed.
But there is a new Problem:
Code:
E/Cryptfs ( 311): Error writing crypto_blkdev /dev/block/dm-0 for f2fs inplace encrypt
I/f2fs_sparseblock( 311): func error
E/Cryptfs ( 311): Error in running over f2fs blocks
E/Cryptfs ( 311): Failed to encrypt f2fs filesystem on /dev/block/bootdevice/by-name/userdata
I/Cryptfs ( 311): Encrypted to block -1
D/Cryptfs ( 311): cryptfs_enable_inplace_f2fs()=-1
E/Cryptfs ( 311): Encrypting filesystem in place...
E/Cryptfs ( 311): Cannot seek to previously encrypted point on /dev/block/dm-0
D/Cryptfs ( 311): cryptfs_enable_inplace_full()=-1
W/SocketClient( 311): write error (Broken pipe)
W/SocketClient( 311): Unable to send msg '200 9 -1'
Have someone a idea?
The Filesystem from the Data Partition is correct...

Error executing updater binary in zip
untrackable said:
Hallo,
i got the new Moto X Play, it should replace my Z1.
Flashing CM is normaly not a real problem for me, but the lux is tricky - i hope you can help me...
adb sideload cm-12.1-20150921-UNOFFICIAL-lux.zip
throws the same error as flashing with TWRP: "E: Error while executing updater binary in zip..."
The TWRP is from here:
http://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
The ROM is from here (SEP21):
http://forum.xda-developers.com/moto-x-play/orig-development/rom-cyanogenmod-moto-x-play-t3205422
The phone is a new XT1562 without provider branding...
Thanks for your help!
untrackable
Click to expand...
Click to collapse
same error even i got unable to figure out :/

solved
untrackable said:
Hallo,
i got the new Moto X Play, it should replace my Z1.
Flashing CM is normaly not a real problem for me, but the lux is tricky - i hope you can help me...
adb sideload cm-12.1-20150921-UNOFFICIAL-lux.zip
throws the same error as flashing with TWRP: "E: Error while executing updater binary in zip..."
The TWRP is from here:
http://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
The ROM is from here (SEP21):
http://forum.xda-developers.com/moto-x-play/orig-development/rom-cyanogenmod-moto-x-play-t3205422
The phone is a new XT1562 without provider branding...
Thanks for your help!
untrackable
Click to expand...
Click to collapse
u must be doing a dirty flash , clear dalvik cache and data and try

jasonhosu said:
u must be doing a dirty flash , clear dalvik cache and data and try
Click to expand...
Click to collapse
This Problem is fixed. Do you have a idea for the encryption problem?

fix
untrackable said:
This Problem is fixed. Do you have a idea for the encryption problem?
Click to expand...
Click to collapse
download the latest build and retry i posted a rom , pac man for moto x play and it worked fine when i did a clean flash

jasonhosu said:
download the latest build and retry i posted a rom , pac man for moto x play and it worked fine when i did a clean flash
Click to expand...
Click to collapse
Oh i tried the latest build (October 12 Release from here)
...but i dont tried pac man...

The encryption problems are not in the version from @h2o64:
http://forum.xda-developers.com/moto-x-play/orig-development/rom-cyanogenmod-12-1-t3222623

Related

[Q] CyanogenMod stuck at splash screen

Hi all,
I have a nexus 7 bought a week ago. I decided to flash CM.
I started with the CM installer as it was suggested on the CM website, but eventually, it said that my device is not supported and I have to install CM by hand. In the process, I believe I rooted my nexus 7.
So I installed ClockworkMod and tried to install various CM images: stable, RC, nightly build ,etc. Every time it is stuck at the splash screen. I can wait for 15 minutes it does go beyond it...
Just in anticipation of some questions: in CWM, I do a "factory reset/user data wipe", "cache wipe" and "dalvik cache wipe" every time before I attempt to install CM. Sometimes I even did it twice each, but that doesn't work any better...
I also tried to install SuperSU while in CWM recovery just to be sure my device in rooted, but CM still does not get beyond the splash screen...
Right now, CM stable 10.2.0 is installed and show this problem.
Would anyone have a clue?
Thank you so much for your help!
you may be flashing grouper, which is the nexus 7 original, this is the nexus 7 2013, known as flo, so make sure you have the correct file
matt4321 said:
you may be flashing grouper, which is the nexus 7 original, this is the nexus 7 2013, known as flo, so make sure you have the correct file
Click to expand...
Click to collapse
I got the ROMs from here: download.cyanogenmod.org/?device=flo&type=
Or maybe I don't understand your comment?...
BTW, I downloaded a AOSP image here: download.paranoidandroid.co/roms/flo/pa_flo-4.0-BETA2-20140113.zip
I flashed it, and again it does not go beyond the splash screen!!!
I can see the google 4 colours moving blob, and it does not go beyond that.
I tried to flash the latest official image (4.4.2) from here: dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz
but CWM give me an error saying 'install aborted', without giving any detail about what went wrong...
Any idea anyone?
Thank you very much for any help, that would be really appreciated!
Alternatively, if someone could tell how to get back to the original state, I would have at least a working device...
seeker6 said:
I got the ROMs from here: download.cyanogenmod.org/?device=flo&type=
Or maybe I don't understand your comment?...
BTW, I downloaded a AOSP image here: download.paranoidandroid.co/roms/flo/pa_flo-4.0-BETA2-20140113.zip
I flashed it, and again it does not go beyond the splash screen!!!
I can see the google 4 colours moving blob, and it does not go beyond that.
I tried to flash the latest official image (4.4.2) from here: dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz
but CWM give me an error saying 'install aborted', without giving any detail about what went wrong...
Any idea anyone?
Thank you very much for any help, that would be really appreciated!
Alternatively, if someone could tell how to get back to the original state, I would have at least a working device...
Click to expand...
Click to collapse
Okay, you're not stuck at the splash screen since you can see the coloured google blobs, that's the boot animation. Did you see the cyanogenmod boot animation? or was it just stuck at the google logo?
Keep in mind that this is the first time you've flashed it so it can take a long time for it to boot up, can sometimes be longer than 5mins, how long are you leaving before you give up?
and flo is the correct device so you are flashing the right file
matt4321 said:
Okay, you're not stuck at the splash screen since you can see the coloured google blobs, that's the boot animation. Did you see the cyanogenmod boot animation? or was it just stuck at the google logo?
Keep in mind that this is the first time you've flashed it so it can take a long time for it to boot up, can sometimes be longer than 5mins, how long are you leaving before you give up?
and flo is the correct device so you are flashing the right file
Click to expand...
Click to collapse
Thanks for your comments, matt4321.
The "google blobs" or the "cyanogenmod spinning circle" are what I meant by splash screen. I do see the white "google" logo for a few seconds, that whatever animation is used for the rom.
I waited for more than 30 minutes both for the AOSP rom and the CyanogenMod rom... I would be surprised if that was normal...
seeker6 said:
Thanks for your comments, matt4321.
The "google blobs" or the "cyanogenmod spinning circle" are what I meant by splash screen. I do see the white "google" logo for a few seconds, that whatever animation is used for the rom.
I waited for more than 30 minutes both for the AOSP rom and the CyanogenMod rom... I would be surprised if that was normal...
Click to expand...
Click to collapse
That is unusually long. Talk me through your exact procedure you are doing.
Are you familiar with fastboot?
Can you type 'fastboot getvar all' and post the result
Sent from my LT30p using Tapatalk
matt4321 said:
That is unusually long. Talk me through your exact procedure you are doing.
Are you familiar with fastboot?
Can you type 'fastboot getvar all' and post the result
Sent from my LT30p using Tapatalk
Click to expand...
Click to collapse
Here is what I did:
1 - Went to cyangenmod website with the nexus 7 browser
2 - Followed the instructions about the CM installer
3 - Installed the necessary software on windows 7, and CM software tells me the installer does not support my device, I have to install it manually
4 - Rebooted in bootloader mode, unlock using 'fastboot oem unlock'
5 - Flashed CWM touch 6.0.4.3 using 'fastboot flash recovery recovery-clockwork-touch-6.0..4.3-flo.img'
6 - Rebooted in recovery mode
7 - In CMW, selected 'wipe data/factory reset', then 'wipe cache partition', then 'advanced->wipe dalvik cache'
8 - Then selected 'install zip from sideload'; the CWM menu now has only 2 options: cancel sideload and +++go back+++
9 - Send image file: 'adb sideload cm-10.2.0-flo.zip'
10 - Wait for a few minutes
11 - CWM now says 'Installing update...' and a little progress bar
12 - After a few seconds, the progress bar disappears and the menu goes back to normal
13 - Select 'go back', then 'reboot system now'
14 - Got stuck at the rotationg CM splash screen
15 - Repeated the flash operation with different CM ROMs, same results
16 - Installed SuperSU, just in case
17 - Repeated operation with AOSP ROM, same result
18 - I just did it with CleanROM-2.6.zip, still stuck at google blobs
Arg!
Result of 'fastboot getvar all' (when in bootloader mode):
(bootloader) version-bootloader: FLO-03.15
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 16G
(bootloader) serialno: 071ecad2
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: unlocked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x000000031b3fbe00
all:
finished. total time: 0.026s
seeker6 said:
Here is what I did:
1 - Went to cyangenmod website with the nexus 7 browser
2 - Followed the instructions about the CM installer
3 - Installed the necessary software on windows 7, and CM software tells me the installer does not support my device, I have to install it manually
4 - Rebooted in bootloader mode, unlock using 'fastboot oem unlock'
5 - Flashed CWM touch 6.0.4.3 using 'fastboot flash recovery recovery-clockwork-touch-6.0..4.3-flo.img'
6 - Rebooted in recovery mode
7 - In CMW, selected 'wipe data/factory reset', then 'wipe cache partition', then 'advanced->wipe dalvik cache'
8 - Then selected 'install zip from sideload'; the CWM menu now has only 2 options: cancel sideload and +++go back+++
9 - Send image file: 'adb sideload cm-10.2.0-flo.zip'
10 - Wait for a few minutes
11 - CWM now says 'Installing update...' and a little progress bar
12 - After a few seconds, the progress bar disappears and the menu goes back to normal
13 - Select 'go back', then 'reboot system now'
14 - Got stuck at the rotationg CM splash screen
15 - Repeated the flash operation with different CM ROMs, same results
16 - Installed SuperSU, just in case
17 - Repeated operation with AOSP ROM, same result
18 - I just did it with CleanROM-2.6.zip, still stuck at google blobs
Arg!
Result of 'fastboot getvar all' (when in bootloader mode):
(bootloader) version-bootloader: FLO-03.15
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 16G
(bootloader) serialno: 071ecad2
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: unlocked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x000000031b3fbe00
all:
finished. total time: 0.026s
Click to expand...
Click to collapse
So you definitely have a flo version. Try to install zip from sdcard on the device rather an adb sideload.
Put CMxxxxxxx-flo-xxxx.zip on your tablet, then in recovery go to install zip from sdcard, choose zip from sdcard then select the zip and install it
Sent from my LT30p using Tapatalk
matt4321 said:
So you definitely have a flo version. Try to install zip from sdcard on the device rather an adb sideload.
Put CMxxxxxxx-flo-xxxx.zip on your tablet, then in recovery go to install zip from sdcard, choose zip from sdcard then select the zip and install it
Sent from my LT30p using Tapatalk
Click to expand...
Click to collapse
There is no sdcard on the nexus 7. There is a /sdcard directory on the device, though. I can 'adb push' the 'cm-10.2.0-flo.zip' file into the '/sdcard' directory on the device. But when I select 'choose zip from /sdcard' if CWM, CWM gives me an error 'E:Can't mount /sdcard' and does not go any further...
seeker6 said:
There is no sdcard on the nexus 7. There is a /sdcard directory on the device, though. I can 'adb push' the 'cm-10.2.0-flo.zip' file into the '/sdcard' directory on the device. But when I select 'choose zip from /sdcard' if CWM, CWM gives me an error 'E:Can't mount /sdcard' and does not go any further...
Click to expand...
Click to collapse
Mount the sdcard in 'mounts and storage'
Sent from my Nexus 7 2013 using Tapatalk
matt4321 said:
Mount the sdcard in 'mounts and storage'
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
Hi,
In 'mounts and storage', there is no option to mount (or unmount) the sdcard.
That would make sense anyway, because what mass storage should it mount there since there is no sd card?
Would you know a website with instructions on how to go back to the original state (including the original recovery rom)?
Many thanks!
seeker6 said:
Hi,
In 'mounts and storage', there is no option to mount (or unmount) the sdcard.
That would make sense anyway, because what mass storage should it mount there since there is no sd card?
Would you know a website with instructions on how to go back to the original state (including the original recovery rom)?
Many thanks!
Click to expand...
Click to collapse
The internal memory is classed as the sdcard.
Yeah you need to fastboot flash all the factory images from the Google developer site
Sent from my LT30p using Tapatalk

[Q] Bricked Moto Razr M, tried multiple options, please help.

Hey guys,
I'm new to learning about the technical details of the Android system, and specifically my MOTO RAZR M. Yesterday my phone lost power, then was sent into a boot loop. The only functional feature from the boot menu is the AP Fastboot function. All the other options just take me back into the boot loop. Ive tried RSD, and Droid utility, with no success. All of them return an error and "FAIL." My guess would be that i'm tying the wrong version? If anyone can give me a point in the right direction, or any assistance at all, that would be great. Thanks!
IDK if this information helps, but here it is
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version-bootloader: 109B(*)
(bootloader) product: smq
(bootloader) secure: yes
(bootloader) mid: 0058
(bootloader) version: 0.5
(bootloader) qe: qe 0/1
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 8GB
(bootloader) reason: Boot menu selected
(bootloader) revision-hardware: 0x82A0
(bootloader) cpu: MSM8960 CS
(bootloader) uid: BBACD70802000100000000000000
(bootloader) cid: 0x02
all:
finished. total time: 0.659s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>
Bump, because i could really use some guidence, even the right reading material
The reason it's failing would help a lot more. What's it saying in RSD?
BTW, I'm in No-Dak too. Cool to see someone else on such a busy website.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
The reason it's failing would help a lot more. What's it saying in RSD?
BTW, I'm in No-Dak too. Cool to see someone else on such a busy website.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
When trying to use RSD lite to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml, i ge tthe following on the phone:
update gpt_main version failed
preflash validation failed for GPT
RSD lite stops at 1/19 with a similar message.
Okay, you're getting that message because you're flashing an older FW. Flash FE the same or newer as what was on your phone.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Okay, you're getting that message because you're flashing an older FW. Flash FE the same or newer as what was on your phone.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So a 4.4.2 will work, regardless? Also, do you know where I can find that file? Ive had trouble looking for it.
Here's a link to all the FW. 4.4.2 should work to clear the fail: http://www.drdevs.com/devs/FXZ-files/XT907 (Droid RAZR M)/
RikRong said:
Here's a link to all the FW. 4.4.2 should work to clear the fail: http://www.drdevs.com/devs/FXZ-files/XT907 (Droid RAZR M)/
Click to expand...
Click to collapse
I tried it with VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml, and still failed on the 1/17 on GPT.bin, oddly enough? What could be causing this?
bump again, really need to get my phone working?
I thought flashing the latest version would always work regardless?
northdakota2170 said:
bump again, really need to get my phone working?
I thought flashing the latest version would always work regardless?
Click to expand...
Click to collapse
Sorry, I'm not good on the technical stuff, but it looks like you're getting some good help on DR.
Sent from my HTC6525LVW using Tapatalk
Hey guys, I used house of moto with the 4.4.2 file, and was successfully able to restore my phone. Thanks for the help!
I had a similar issue with my XT905 (Australian RAZR M)
Lost power due to a dead battery, and after it charged and started up, it entered a continuous boot loop. I could access recovery and the bootloader, so I attempted to reinstall multiple firmwares using fast boot, RSD Lite, or through a recovery (CWM and TWRP) but had no luck booting any. This was a week or so ago.
Just found this thread today and as I've never used the HouseOfMoto utitlity I thought I'd give it a shot. I installed the stock Telstra jellybean firmware using it and it successfully booted an OS for the first time. I can only assume the HouseOfMoto utility installs ROMs in a different fashion from RSD Lite. Had to be a jellybean ROM as the kitkat bootloader isn't out for the XT905 yet.
If anyone else has a similar issue please give this method a shot.
justin89h said:
I had a similar issue with my XT905 (Australian RAZR M)
Lost power due to a dead battery, and after it charged and started up, it entered a continuous boot loop. I could access recovery and the bootloader, so I attempted to reinstall multiple firmwares using fast boot, RSD Lite, or through a recovery (CWM and TWRP) but had no luck booting any. This was a week or so ago.
Just found this thread today and as I've never used the HouseOfMoto utitlity I thought I'd give it a shot. I installed the stock Telstra jellybean firmware using it and it successfully booted an OS for the first time. I can only assume the HouseOfMoto utility installs ROMs in a different fashion from RSD Lite. Had to be a jellybean ROM as the kitkat bootloader isn't out for the XT905 yet.
If anyone else has a similar issue please give this method a shot.
Click to expand...
Click to collapse
On my second reboot it entered a boot loop again so scratch that advice. Probably a hardware issue like I originally thought

Help me pls ! I m Need Htc M9+ Ota File ...

C:\Users\Hakan>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXX
(bootloader) version-main: 1.86.401.7
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__J15
all:
finished. total time: 0.003s
Telephone status S-OF & Unlocked
hello friends, I wrote phone information. phone system came update. The new update file appears as 1.90.401.3, but not tamamyal system update for the Twrp Recovery is installed. I was in the Recovery menu. According to information I'm looking for my phone for OTA update files. Thank you in advance for your friends to help you.
Hello friend, you must firstly flash stock recovery to OTA. On the top of that, you should have an unmodified system partition.
Sent from my HTC_M9pw using XDA Free mobile app
yvtc75 said:
Hello friend, you must firstly flash stock recovery to OTA. On the top of that, you should have an unmodified system partition.
Sent from my HTC_M9pw using XDA Free mobile app
Click to expand...
Click to collapse
thank you. I'm a bit novice in these matters. can you help me on stock recovery ? I share my phone 's information . You can write me just ask you this information in accordance with the appropriate link to the original recovery . My download and load . I will be very happy if you help .
Thank you I am waiting for the help
I noted your device was s-offed.
Use this RUU
http://forum.xda-developers.com/one-m9/one-m9-general/ruu-htc-one-m9-1-85-401-6-t3218717
And the flash procedure was included in the bellow post .
http://forum.xda-developers.com/showpost.php?p=61801034&postcount=8
Backup your data first and good luck!!
Sent from my HTC_M9pw using XDA Free mobile app
If you only want stock recovery for simple OTA, ask jirkab for help.
http://forum.xda-developers.com/one-m9/one-m9-general/ota-1-90-401-3-europe-wwe-m9-t3299433
yvtc75 said:
I noted your device was s-offed.
Use this RUU
http://forum.xda-developers.com/one-m9/one-m9-general/ruu-htc-one-m9-1-85-401-6-t3218717
And the flash procedure was included in the bellow post .
http://forum.xda-developers.com/showpost.php?p=61801034&postcount=8
Backup your data first and good luck!!
Sent from my HTC_M9pw using XDA Free mobile app
If you only want stock recovery for simple OTA, ask jirkab for help.
http://forum.xda-developers.com/one-m9/one-m9-general/ota-1-90-401-3-europe-wwe-m9-t3299433
Click to expand...
Click to collapse
Thank you for helping .
ota_hıau_ml_tuhl_l50_sense70_mr_htc_europe_1.90.401.3-1.86.401.7_release_464403.zip file I uploaded on my sd card. Then I upload the files from the recovery menu. However, E : I get the error Zip signatures verified . How do I resolve this error.
To resolve the errors I made my phone super- serious. but it did not happen.
Do you have any idea how to fix this error? I am still waiting for version 1.86.401.7
GoodyCruz said:
Thank you for helping .
ota_hıau_ml_tuhl_l50_sense70_mr_htc_europe_1.90.401.3-1.86.401.7_release_464403.zip file I uploaded on my sd card. Then I upload the files from the recovery menu. However, E : I get the error Zip signatures verified . How do I resolve this error.
To resolve the errors I made my phone super- serious. but it did not happen.
Do you have any idea how to fix this error? I am still waiting for version 1.86.401.7
Click to expand...
Click to collapse
these as detailed by the howtos linked by the previous post, are not flashable from custom recovery. You need stock recovery not a custom like TWRP.
Or rather be using Fastboot tool from a PC, that's the most convenient in your situation i think

Latest Firmware for XT 1686 Indian Variant.

Hi guys finally i managed to unbrick the hard bricked phone ...
now my question is how should i choose the stock firmware for my device which is Indian variant - XT1686 32 GB
Bcoz as there are lots of different variants .... i have tried brazil
XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2017-02-05
this doesnt give IMEI numbers it will make them 0 so can u guys please tell me how should i choose the variants
and also please if some one have the recent boot loader.img, recovery.img and gpt.bin please provide me im stuck in boot loop ... just the sake until we get oreo update - XT1686 is my phone
i am not able to use my phone right now request you guys....
It's normal not to have your IMEI on stock if you've flashed Oreo ROMs before.
You can follow instructions in this thread if you want to get IMEI back.
Happy flashing!
Jrhotrod said:
It's normal not to have your IMEI on stock if you've flashed Oreo ROMs before.
You can follow instructions in this thread if you want to get IMEI back.
Happy flashing!
Click to expand...
Click to collapse
now actually my phone is stuck with Moto Z2 play boot loader so that i need everything to be Moto z2 play's firmware .... to wake up the dead phone it took me around 4 hours .... So my boot loader is not letting me install any other firmwares on my phone
please help me :crying:
This is what i got when i tried to flash Moto g5 plus Boot loader by downloading all the firmwares from official website:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.118s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.405s
praveen Glaxi said:
now actually my phone is stuck with Moto Z2 play boot loader so that i need everything to be Moto z2 play's firmware .... to wake up the dead phone it took me around 4 hours .... So my boot loader is not letting me install any other firmwares on my phone
please help me :crying:
This is what i got when i tried to flash Moto g5 plus Boot loader by downloading all the firmwares from official website:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.118s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.405s
Click to expand...
Click to collapse
What on Earth did you do to get the Z2 bootloader and how did you get it to even flash in the first place?
Jrhotrod said:
What on Earth did you do to get the Z2 bootloader and how did you get it to even flash in the first place?
Click to expand...
Click to collapse
Okay dude .... Let me explain very quickly ....
First off I bought this device like 8 months ago .... 1 week b4 I flashed customs ROM that is lineago os 15.1 which was recent for my device .... Everything was fine until yrstdy.... Yrstdy morning what I did was I planned to flash normal stock ROM to my phone .... Using some brasil version by watching YouTube ... Everything went well I was like thank god and then I inserted the sim but there was not network due to imei issue ....
This is where problem started...
Thinking after I do the OTA update security patch might go back and I might get the signal but then I did ota update and phone restarted ... It showed installing updates in half wat it suddenly switched I realised that I hard bricked my phone ...
Then searched the whole xda forums and found this guide https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457/page6
By Rakesh1b.....
I did the same I used potter blank flash and my phone woke up after trying it several hours....
Then when I tried to flash bootloader of moto g5 plus it showed error like I previously displayed ..... Well there was one more post for all of these 3 files, bootloader.IMG gpt.bin and recovery.IMG well I did flash all of them they seem to be worked ...
Then I tried to flash moto g5 plus twrp recovery which gave me error of failure...
Then I tried moto z2 play twrp ... God damn it got flashed and went into twrp recovery then as I studied as per @Rakesh1b ......
And now I'm stuck here ..... Not able to go front...
I get error like /cache not found when I try to flash custom os ...
What all I need now is moto g5 plus boot loader.IMG recovery.IMG gpt.bin
Of January security patch ... Mine last update was November security patch
I request some one to give those files or give a proper solution for this plzzzzzz
praveen Glaxi said:
I did the same I used potter blank flash and my phone woke up after trying it several hours....
Then when I tried to flash bootloader of moto g5 plus it showed error like I previously displayed ..... Well there was one more post for all of these 3 files, bootloader.IMG gpt.bin and recovery.IMG well I did flash all of them they seem to be worked ...
Then I tried to flash moto g5 plus twrp recovery which gave me error of failure...
Then I tried moto z2 play twrp ... God damn it got flashed and went into twrp recovery then as I studied as per @Rakesh1b ......
And now I'm stuck here ..... Not able to go front...
I get error like /cache not found when I try to flash custom os ...
What all I need now is moto g5 plus boot loader.IMG recovery.IMG gpt.bin
Of January security patch ... Mine last update was November security patch
I request some one to give those files or give a proper solution for this plzzzzzz
Click to expand...
Click to collapse
Thank you for the explanation, your situation seems to (mostly) make sense to me now.
You probably realize this in retrospect, but you should not have accepted an OTA on stock with no IMEI. But enough with that, what exactly do you mean by "my phone woke up"? I'd love to offer you a solution, but to find one, I'll need to know if "waking up" involved booting into Android, booting into the bootloader, or whatever.
u should unlock bootloader first.. the version of bootloader is lower than on ur phone, you should not OTA update, OTA did upgraded ur bootloader ver to latest..
---------- Post added at 06:32 AM ---------- Previous post was at 06:28 AM ----------
Try this firmware for ur model latest from february 2018
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
or
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
---------- Post added at 06:54 AM ---------- Previous post was at 06:32 AM ----------
[/COLOR]if u followed this solution and unbricked ur devices,try this Rom
its debloated and deodexed stock rom
: https://doc-00-6o-docs.googleuserco...2322377&hash=4s4e5hh6kltpi7nthp0actt4434mbjof
Orginal post :
https://forum.xda-developers.com/g5-plus/development/stock-debloated-deodexed-t3619972
THE FIRST THING U SHOULD TO UNLOCK BOOTLOADER before to try and CWM OR TWRP, custom rom..
Hey guys thanks for everyone's assistance here
i have successfully flashed Pixel experience ROM to my phone by using this procedure
1st. Blank flash your phone as per the above procedure..... (disable signature enforcement if u are using windows 10)
press and hold power button you could hear that mobile disconnects and connects once you hear that then press voldown and power with one hand and run blankflash.bat and then release those buttons before u hear them again
2nd. Flash all 3 provided files in MotoG5Plus_addison2Potter in the attachement and it will take you to the boot loader
Using these Commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Fastboot flash recovery recovery.img
fastboot reboot-bootloader
(Flash the files from provided Zip attachment)
3rd. download Moto z2 play or plus twrp recovery as i didnt have time to compress everything i cud nt provide that, then flash the custom recovery, then try to enter into recovery mod and it should enter..... if u have done 1st and 2nd step properly then u will enter into TWRP recvery mod
and here is the link for debolated ROM download version 2 which has november patch on it....
https://forum.xda-developers.com/g5-...dexed-t3619972
then once ur in twrp mount it to ur pc and copy the debolate ROM to ur phone and then flash it though TWRP ....
once it is done reboot ur phone into os and it should successfully boot into ROM...
once done u can flash any custom ROM into ur phone using TWRP
But 1 major issue is that i lost 4g or VoLTE:
Can u guys please help me with that.....

OS for XT1761 Please

I have hours and lots of GB of bandwidth wasted trying every ROM edition i found about "Moto E4", when i try to install it says "...this package is for device xxxxx, this device is perry"
Nothing worked so far also i didn't create a backup and i can't even find how to turn it back as it was
Can someone please help me maybe there's something i can do or any version i haven't seen?
I'm very new i don't have much knowledge about androids but i learn fast and i have huge knowledge on linux/windows.
daraw said:
I have hours and lots of GB of bandwidth wasted trying every ROM edition i found about "Moto E4", when i try to install it says "...this package is for device xxxxx, this device is perry"
Nothing worked so far also i didn't create a backup and i can't even find how to turn it back as it was
Can someone please help me maybe there's something i can do or any version i haven't seen?
I'm very new i don't have much knowledge about androids but i learn fast and i have huge knowledge on linux/windows.
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
Official firmware
https://mirrors.lolinet.com/firmware/moto
Or use LMSA'S flash/rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
sd_shadow said:
run
Code:
fastboot getvar all
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
Official firmware
https://mirrors.lolinet.com/firmware/moto
Or use LMSA'S flash/rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Code:
fastboot getvar all
(bootloader) serialno: ZY32298X8N
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) efuse: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: WOODS
(bootloader) hwid: 31
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
Thanks to you i found ROM at https://mirrors.lolinet.com/firmware/moto/woods/official/oem/
since my Moto E4 says Woods from fast boot, and on screen reports SKU : XT1761
i've download xt1761_fastboot_woods_oem_user_7.1.1_NMA26.42-11-3_3_release-keys_oem_EMEA
this zip also includes a "recovery.img" is that the stock recovery? i tried to boot it with fastboot but i got this error
Code:
C:\Users\DOPE-PC\Desktop\xt1761_fastboot_woods_oem_user_7.1.1_NMA26.42-11-3_3_release-keys_oem_EMEA>fastboot boot recovery.img
creating boot image...
creating boot image - 11888640 bytes
Sending 'boot.img' (11610 KB) OKAY [ 0.346s]
Booting FAILED (remote: 'invalid kernel address: not lie in memory')
fastboot: error: Command failed
do you have any idea if that's recovery image or something else? also is possible to flash ROM from TWRP or fastboot cli, i tried some other program called "SP_Flash_Tool_v5.1952_Win" but when i open it and try to flash it doesn't connect to my phone :crying:
daraw said:
run
Thanks to you i found ROM at https://mirrors.lolinet.com/firmware/moto/woods/official/oem/
since my Moto E4 says Woods from fast boot, and on screen reports SKU : XT1761
i've download xt1761_fastboot_woods_oem_user_7.1.1_NMA26.42-11-3_3_release-keys_oem_EMEA
this zip also includes a "recovery.img" is that the stock recovery? i tried to boot it with fastboot but i got this error
do you have any idea if that's recovery image or something else? also is possible to flash ROM from TWRP or fastboot cli, i tried some other program called "SP_Flash_Tool_v5.1952_Win" but when i open it and try to flash it doesn't connect to my phone :crying:
Click to expand...
Click to collapse
There's some woods flashing instructions in
https://forum.xda-developers.com/moto-e4/how-to/stock-os-moto-e4-sku-version-xt1760-t3719075
Just for update,
after hours trying i was able to install lineage-15.0-20171216_090858-UNOFFICIAL-nicklaus.zip
however phone stuck in a bootloop, so i gave up and started testing SP flash tool and managed to get stock android back and working as normal.
My point was to get android 9 or 8, if anyone knows or has any idea how to please let me know
i'm talking about Moto E4 (Woods), XT1761,
TWRP Version that's working for me twrp-3.2.2-0-woods.img
other then that i've tested lots of ROM i got none working (was able to install LineageOS 15.0 but ended on bootloop)
daraw said:
Just for update,
after hours trying i was able to install lineage-15.0-20171216_090858-UNOFFICIAL-nicklaus.zip
...
Click to expand...
Click to collapse
Make sure they say woods
Nicklaus is E4 Plus XT1776
https://forum.xda-developers.com/moto-e4/development
Sent from my ali using XDA Labs
sd_shadow said:
Make sure they say woods
Nicklaus is E4 Plus XT1776
https://forum.xda-developers.com/moto-e4/development
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
yeah i tested a lot saying woods none of them worked cause of no SKU match, as far as i've been looking there's no custom ROM for Moto E4 woods, XT1761

Categories

Resources