Develop Bugs

Help: Bricked Htc one M8 GPe

Hello everyone, I started to play around with all the diff things you can do with a rooted phone had plans for getting a custom ROM for my phone. Let me stat by saying that I am very new to all this.
I day ago i was getting ready to install the custom ROM for viper (ViperOneM8_1.7.1) reason being is coming from a htc one m7 with sense i wanted to get back to sense from my stock GPe m8.
I was able to unlock my bootloader and get my phone rooted I fallowed this video (How to Root your HTC One M8 - Full Guide) From Sakitech... or least I think im rooted still... I'll come back to you as to why I say "I think I'm rooted".
I thought it would be very simple just fire up the custom recovery and flash the ROM and sit back while it flashed, well everything went down hill from this point. Let me tell you what i did.
First i got to the custom recovery and I did a wipe I did advanced wipe and checked the boxes this is where I think I deleted the OS(after this I could not get back on the phone to do anything only will boot to recovery and it say no OS installed then asks if I want to get SuperSU installed this is where I already thought I was rooted but maybe on not??? I'm very confused about that
Then I used the sideload method to push the rom zip and try to flash the rom at this point I cant get it to flash. First I was getting the MD5 error I checked that off now it will just fail either saying error executing the binary from the zip or that zip is corrupted. (I tried re-downloading the ROM even from mirror link)
At this point I am very frustrated and feel helpless. I tried my best to keep from posting this and try to research to see if i can find the solution myself but I'm having no luck I have my days off from work to get my phone up and running or ill just have to go but another phone. At this point I really need some help. All I want is a working phone if i can get back to GPe stock that would be fine or make the ViperOne work.
Attempts to solve my problem: I tried flashing GPE4.4.3_m8.zip and other stock GPe ROMs nothing works
Thanks for reading and all your help I will sit nest to my comp and answer anything to try make everything as clear as possible. Thank you again

So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?

Demonwarrior said:
So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?
Click to expand...
Click to collapse
no offense, buy you need to read before you continue anything else.

rbouza1 said:
no offense, buy you need to read before you continue anything else.
Click to expand...
Click to collapse
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?

Demonwarrior said:
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?
Click to expand...
Click to collapse
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....

Mr Hofs said:
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....
Click to expand...
Click to collapse
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed

Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
fastboot flash img boot.img
---------- Post added at 06:28 PM ---------- Previous post was at 06:25 PM ----------
try that command, and what model did you have originally and did you convert to gpe or flash a gpe ROM.

gave me an error
Code:
FAILED (remote: signature verify fail)
Its a stock Google play edition I bought from the Google paly store, I didnt flash any other rom the ViperOne rom was going to be the first flash on the phone

Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.

iHagbani said:
Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.
Click to expand...
Click to collapse
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.

Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589

ckpv5 said:
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you

Demonwarrior said:
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.
Click to expand...
Click to collapse
I know, but I told you this way in case that the adb didn't flash the whole zip file!

Demonwarrior said:
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you
Click to expand...
Click to collapse
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)

j to the 4n said:
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)
Click to expand...
Click to collapse
I tried the instruction on the thread it didnt work... I think its because i have s-on
Code:
C:\Users\owner\Desktop\htc one\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.058s]
finished. total time: 0.061s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.483s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.846s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.484s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.665s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.479s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.662s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.478s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.661s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.458s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.641s
C:\Users\owner\Desktop\htc one\platform-tools>
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.470s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.650s
C:\Users\owner\Desktop\htc one\platform-tools>
The post says to try it a few times but still giving me the say error

TWRP - Failed to mount '/firmware' (invalid argument)

I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!

gocks said:
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
Click to expand...
Click to collapse
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.

dandrumheller said:
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
Click to expand...
Click to collapse
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??

gocks said:
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
Click to expand...
Click to collapse
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using
Click to expand...
Click to collapse
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.

gocks said:
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
Click to expand...
Click to collapse
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.

gocks said:
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
Click to expand...
Click to collapse
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!

gocks said:
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
Click to expand...
Click to collapse
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did exactly what you told me and this happened:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.683s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10820 KB)...
OKAY [ 0.235s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.235s]
finished. total time: 0.501s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257307 KB)...
OKAY [ 5.493s]
writing 'system'...
OKAY [ 3.985s]
finished. total time: 9.478s
The othes lines seems to be ok, but the phone continue stucked on the "Your device has been unlock...." and don´t reboot.

Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.

gocks said:
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
Click to expand...
Click to collapse
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.

gocks said:
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
Click to expand...
Click to collapse
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws

flashallthetime said:
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
Click to expand...
Click to collapse
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?

gocks said:
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
Click to expand...
Click to collapse
Which carrier are you with?
And don't sue me if things get worse

flashallthetime said:
Which carrier are you with?
And don't sue me if things get worse
Click to expand...
Click to collapse
Vivo, its a brazilian one.
Relax, if my phone bricks I wont sue you because my wife will kill me first!

I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat

gocks said:
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
Click to expand...
Click to collapse
Yes and it seems like you can't right to the system and or data partitions. There's more partitions but they're locked or hidden
Try to format your data in TWRP
and wipe system

Can't flash TWRP - remote failure (SOLVED)

Hi guys!
I hope you can help me, since I've looked everywhere but can only find people with similar but not the exact same problem.
I tried flashing TWRP in order to migrate to a custom ROM. I am currently running official 7.1.1.
When I try to flash twrp (tried several versions) the command window shows me this:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.068s
I tried using Moto fastboot as well but with the same result. I'd really appreciate your help. Please note, that I am not a pro like most you guys so I might have follow-up questions

Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?

Artim_96 said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?
Click to expand...
Click to collapse
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s

Okay, I managed to unlock the bootloader with the unlock key I got from Motorola.
Now when I try to flash it says:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.280s]
finished. total time: 0.330s
Come ooooon

ischariot_pasadelski said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s
Click to expand...
Click to collapse
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary

Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.

I figured it out.
I had to restore the file system by only checking the "System" box when wiping with TPWR - just in case anybody else has the same problems.

So a factory data reset solve the problem? Having your first issue with moto e5 cricket and you can't unlock three bootloader

Artim_96 said:
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary
Click to expand...
Click to collapse
well, i had it unlocked via the settingsbutton and after read this here , via the website where you can get the 20 bits code, but it is the same result with a code that is the same as the adb devices code, just as before! Only thing that is changed is a warning when you starts the phone up.

ischariot_pasadelski said:
Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.
Click to expand...
Click to collapse
Can you tell me how you got the phone twrped, pls?

Huge problem with moto z2 play trying to flash twrp

Hi. Today I decided to root my device (Moto Z2 Play, XT1710-06) and install a good custom ROM, but after unlocking bootloader I tried to flash the recovery with the command fastboot
PHP:
flash recovery twrp.img
and I got the message
PHP:
error: cannot open 'twrp.img'
. So I went with the newest version for albus (twrp-3.2.3-0-albus.img) and I got this:
PHP:
target reported max download size of 534773760 bytes
sending 'recovery' (15564 KB)...
OKAY [ 0.344s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.195s]
finished. total time: 0.539s
After partially flashed it I could only use it once. When rebooting to system (stock) it would overwrite the stock recovery, so TWRP would dissapear. Then I decided to root with the stock ROM in but it got bootlooped.
Finally, I flash recovery again so I could wipe (Including data and system) and install a custom ROM, but didn't work yet because the error messages I get in TWRP after trying to flash the ROMs zip is ERROR 255. I have tried with ToxicRom, LineageOS and Pixel Experience.
What's happening? Did I do wrong wiping the stock system? I'll appreciate any help.
Thanks for reading.

Caney said:
Hi. Today I decided to root my device (Moto Z2 Play, XT1710-06) and install a good custom ROM, but after unlocking bootloader I tried to flash the recovery with the command fastboot
PHP:
flash recovery twrp.img
and I got the message
PHP:
error: cannot open 'twrp.img'
. So I went with the newest version for albus (twrp-3.2.3-0-albus.img) and I got this:
PHP:
target reported max download size of 534773760 bytes
sending 'recovery' (15564 KB)...
OKAY [ 0.344s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.195s]
finished. total time: 0.539s
After partially flashed it I could only use it once. When rebooting to system (stock) it would overwrite the stock recovery, so TWRP would dissapear. Then I decided to root with the stock ROM in but it got bootlooped.
Finally, I flash recovery again so I could wipe (Including data and system) and install a custom ROM, but didn't work yet because the error messages I get in TWRP after trying to flash the ROMs zip is ERROR 255. I have tried with ToxicRom, LineageOS and Pixel Experience.
What's happening? Did I do wrong wiping the stock system? I'll appreciate any help.
Thanks for reading.
Click to expand...
Click to collapse
Flash Magisk, after TWRP.

I kinda solved it. Now I'm on Resurrection Remix Oreo but Magisk 18.0 can't be flashed, neither on LineageOs 15.1

I have the xt1710-06 that the operating system is 32 bit from Argentina
I do not know if it's the same cell phone I finally see that someone manages to install the twrp and a custom rom could do a tutorial please?
there is no tutorial for this model and I do not know if you can install a 64bit android in one that has a 32bit operating system
THANKS

Hi, how did you solve it?

Boot TWRP, then flash it from inside TWRP. Flashing from fastboot always throws some error, but just booting the same image has no problem. And of course TWRP can flash itself.
When flashing Magisk, make sure it keeps dm-verity and enforce encrypt. At least Magisk v19 doesn't give me any problem when setting them before. I think v18 was a version acting up here and there

Can't install TWRP Recovery? Invalid Paratition Recovery

So, I'm trying to get TWRP installed so I can root my phone, but whenever I go to try and do the fastboot flah recovery recovery.img command, I get this:
C:\Users\darks_000\Downloads\platform-tools-latest-windows\platform-tools>fastbo
ot flash recovery recovery.img.img
target reported max download size of 536870912 bytes
sending 'recovery' (26498 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.781s
I'm not sure what to do?

MedievalFreakShow said:
So, I'm trying to get TWRP installed so I can root my phone, but whenever I go to try and do the fastboot flah recovery recovery.img command, I get this:
C:\Users\darks_000\Downloads\platform-tools-latest-windows\platform-tools>fastbo
ot flash recovery recovery.img.img
target reported max download size of 536870912 bytes
sending 'recovery' (26498 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.781s
I'm not sure what to do?
Click to expand...
Click to collapse
1. Make sure your device is unlocked.
2. Make sure fastboot is up to date.
3. That's not how you install twrp. It doesn't get flashed. You boot it temporarily and then use twrp to install itself into your current ramdisk.
4. You must also install a GSI afterwards or twrp will not work correctly. Twrp is not compatible with the stock OS because of some very hellish security Motorola has in place.
5. If you have a Verizon, Cricket, or At&t branded G7 Play, none of the above is possible. If you bought an unlocked or retail model and simply use one of them as a carrier though, it is possible.

Spaceminer said:
1. Make sure your device is unlocked.
2. Make sure fastboot is up to date.
3. That's not how you install twrp. It doesn't get flashed. You boot it temporarily and then use twrp to install itself into your current ramdisk.
4. You must also install a GSI afterwards or twrp will not work correctly. Twrp is not compatible with the stock OS because of some very hellish security Motorola has in place.
5. If you have a Verizon, Cricket, or At&t branded G7 Play, none of the above is possible. If you bought an unlocked or retail model and simply use one of them as a carrier though, it is possible.
Click to expand...
Click to collapse
Device is unlocked. Bootloader is also unlocked. As for fast boot im not sure how to update it. Unless it updates with the system updates. Ive not done them for fear of upgrading the software and then not being able to put twrp on or root it.