Develop Bugs

Possible to rescue the phone?

Hey guys,
my girlfriend has an M9. Saturday it lied idle on the table and rebooted itself. When it booted it just showed the white screen with the HTC logo and the read disclaimer warning.
I rebooted with power off and volume up and the phone just bootlooped all the time. Shows black screen with HTC Logo.
I tried to press the Vol down button on a restart but that didnt work it just bootlooped as before. Then I pressed Vol up +down and could enter the bootloader. From there I entered twrp and tried to wipe the system and then it just shows:
"Could not mount /data and unable to find crypto footer." and it failed to mount /cache , /system, /data, /devlog, /carrier , /cota , /preload and "Unable to mount storage" followed by failes in /data and cache.
Every fail have an (Invalid argument).
I also tried following fastboot commands:
format system
Couldn't parse partition size '0x0X118000000'.
erasing 'system'...
OKAY [ 0.241s]
finished. total time: 0.241s
format data
Formatting is not supported for file system with type ''.
format cache
Couldn't parse partition size '0x0X14000000'.
erasing 'cache'...
OKAY [ 0.270s]
finished. total time: 0.270s
flash zip 0PJAIMG.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
OKAY [ 1.015s]
writing 'zip' 1/1...
(bootloader) HOSD CL#671447
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.209s
The output of getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.161.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_96.00.51201G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: VODAP102
all:
finished. total time: 0.006s
Could someone please tell me if it even possible to rescue the phone? Is there something I forget to try or do somebody know something?
I appreciate every help i could get.
And forgive my bad english.

I think Twrp has gone mental.. If i remember correctly you have to flash back to stock. Follow flippy's thread in the general section.
Beamed in by telepathy.

Thx for the answer first.
I already tried what is shown at the spreadsheet of Flippy. I downloaded the right RUU again and gave it one more try but the same. It appears "Start ui_updating". After a few seconds the screen turns black and it appears the HTC logo on an black screen and it vibrates and turn black agan and again the logo with vibration. If i immediatly try to flash it a second time, itcontinues,shows name of system types but the percent is still 0. When it reaches a certain system type (after 10 or 12) it reboots to the white screen with the green HTC logo and the red disclaimer and stuck there.
Do you have an idea?

I have the same error. We have to do something and solve this. Can you solve it?

you can also just get a backup for twrp, which is matching your cid/mainversion, wipe everything except your internal storage and restore the backup

Like i said at the beginning, its not possible to wipe the partitions. They cant be mounted by twrp. I tried already to install an TWRP Backup with the right CID but even that failed because twrp couldn't write to the partitions.
THX for your answers

Ah fock, at first remove your imei from first post, then tell me if your phone is s-offed or not
Sent from my HTC One M9 using XDA-Developers mobile app

Oh sry overlocked that the imei was there.
The phone is s-on.

get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything

DeeZZ_NuuZZ said:
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
Click to expand...
Click to collapse
It wont work. Phone dont let us to write anything
We cant change cid, mid, lock and unlock bootloader. It is emmc issue. Emmc have to change.
P.s. my phone is s-off.

degerli43 said:
It wont work. Phone dont let us to write anything
We cant change cid, mid, lock and unlock bootloader. It is emmc issue. Emmc have to change.
P.s. my phone is s-off.
Click to expand...
Click to collapse
you should be able to fix it with an install of a RUU. s-off has more chances for that.
the other guy should try to flash the firmware zip in RUU mode, not just normal mode. it should work.. if not he has to get a RUU, if that doesn't work.. yea only RMA or how it is called for you should help. if they won't fix it, sell the device, and get another one

DeeZZ_NuuZZ said:
you should be able to fix it with an install of a RUU. s-off has more chances for that.
the other guy should try to flash the firmware zip in RUU mode, not just normal mode. it should work.. if not he has to get a RUU, if that doesn't work.. yea only RMA or how it is called for you should help. if they won't fix it, sell the device, and get another one
Click to expand...
Click to collapse
When i type fastboot oem rebootRUU the phone rstarting rebooting continuously so i cant flash anything. It s very expensive device here and i love it. I will be so sad if it wont fix

DeeZZ_NuuZZ said:
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
Click to expand...
Click to collapse
Ok when i type fastboot oem lock in the download mode, it restarts and stops again in the bootloop on the HTC logo with blackscreen. If I press Vol UP+DOWN I can see that the device is still unlocked.
Do you have any other ideas? And thx for your help

VGLink said:
Ok when i type fastboot oem lock in the download mode, it restarts and stops again in the bootloop on the HTC logo with blackscreen. If I press Vol UP+DOWN I can see that the device is still unlocked.
Do you have any other ideas? And thx for your help
Click to expand...
Click to collapse
Get the proper HTC fastboot files and try with that...if that doesn't work, your phone is dead..I can't help further, sorry
Sent from my HTC One M9 using XDA-Developers mobile app

Hi, its not possible to enter RUU or to relock or Flash the Phone. It seems its gone dead by itself. Nevertheless thank You for your help .

Rollback to stock failed.

The bootloader are unlocked. But, when I decide to rollback, I started the flash process using "fastboot oem lock begin"; then, every try of flash give me this kind of error, showed bellow.
So, for example, I got this when I tried to flash stock over a lineage rom:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.014s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.184s
What should I do? I have tried to flash bootloader.img and use "fastboot oem fb_mode_set", but stay in the same situation.
Obviously, I'm using the exactly stock versions to my device.
Thank you guys! :laugh:

motafoca55 said:
The bootloader are unlocked. But, when I decide to rollback, I started the flash process using "fastboot oem lock begin"; then, every try of flash give me this kind of error, showed bellow.
So, for example, I got this when I tried to flash stock over a lineage rom:
What should I do? I have tried to flash bootloader.img and use "fastboot oem fb_mode_set", but stay in the same situation.
Obviously, I'm using the exactly stock versions to my device.
Thank you guys! :laugh:
Click to expand...
Click to collapse
All I can say is you should have pulled ur stock ROM

Cant flash recovery error target reported max download size of 536870912 by

I can't flash my recovery.
Bootloader is unlocked.
Phone is not rooted
This sucks becouse i bought this phone thinking i whould not have this ****ing problem again.
(also lost my old one for the millionth time)
PS C:\Users\Admin> fastboot flash recovery C:\ProgramData\chocolatey\lib\adb\tools\platform-tools\twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.473s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.502s
PS C:\Users\Admin>
Click to expand...
Click to collapse

Weird, that validation error is usually shown when bootloader isn't actually unlocked. Have you tried unlocking it again? Have you tried with mfastboot?

DrunkenPanda2000 said:
I can't flash my recovery.
Bootloader is unlocked.
Phone is not rooted
This sucks becouse i bought this phone thinking i whould not have this ****ing problem again.
(also lost my old one for the millionth time)
Click to expand...
Click to collapse
Either you are flashing the wrong recovery for the phone - or you renamed a zip file instead of extracting the img file first
Or
Put quotation marks around the file path eg "c:/file path" or navigate to where you have fastboot and the twrp image first so all you have to type is
fastboot flash recovery recovery.img
Also make sure adb debugging is enabled in dev options of phone settings
Also if the bootloader is unlocked you should get a bootloader unlocked warning when the device starts unless you have replaced the boot logo with a modified one
If you haven't replaced this & you don't get said warning your device doesn't have an unlocked bootloader

The console is definatly finding the file. this is not the issueadb debugging is enabled. altho i realised i have the insert pattern before startup enabled and i think that might be interfering.
I am not gettIng the bootloader unlocked warning.

I disabled the pattern on bootup.
I unlocked with oem unlock.
i tried to flash from directory
Same issue
Stil no unlocked warning
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.493s
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools>
Click to expand...
Click to collapse

DrunkenPanda2000 said:
I disabled the pattern on bootup.
I unlocked with oem unlock.
i tried to flash from directory
Same issue
Stil no unlocked warning
Click to expand...
Click to collapse
Just to check, have you requested and used the unlock key from the Motorola website? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

echo92 said:
Just to check, have you requested and used the unlock key from the Motorola website? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
I have requested one. haven't received it yet.
The website doesn't show if eligable if click that button.
Also they havent send me anything for an houer after requesting.

DrunkenPanda2000 said:
I have requested one. haven't received it yet.
The website doesn't show if eligable if click that button.
Also they havent send me anything for an houer after requesting.
Click to expand...
Click to collapse
Hopefully they'll send you an email with the code in soon. Sometimes the website is a little slow, but regardless it should say if your device is eligible for unlocking. Is your device a carrier bought device or a retail device or bought from Amazon Prime? They do say if your device is bought from Motorola, to wait at least 24 hours before requesting the code.
Check that the unlock string from your device is properly formatted for the website
Ok, so my device should be eligible, but when in enter my unlock string in your tool, I get an error message. What’s wrong?
Please make sure the string you enter in the tool is:
formatted to fit on one line only
has no spaces (you have to remove them manually)
has no carriage returns (these pesky \n)
is of the right length, e.g don’t forget to append the extra 000000… on the last line
USE THE SCRUB TOOL on the UNLOCK PAGE - ABOVE the INPUT BOX
As an example, this is what is returned with the fastboot command
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 99999999999999993332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
And this is what you should enter in the form; it’s a single line, no spaces but with all the trailing zeroes.
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2A 0C39F951A3E5#1F532800020000000000000000000000
Click to expand...
Click to collapse
credit to: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
That code in the email should let you unlock the bootloader and let you flash TWRP, no other way to unlock your bootloader (officially). If you don't get the code after a few tries of the website/waiting for the email, you may have to post on the Motorola forums: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1

Ok so now i unlocked with the code and when i flash i get the following.µ
Model is cedric XT1676 16GB P5
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.469s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.510s]
finished. total time: 0.985s
Seems to be working now.

DrunkenPanda2000 said:
Ok so now i unlocked with the code and when i flash i get the following.µ
Model is cedric XT1676 16GB P5
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.469s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.510s]
finished. total time: 0.985s
Click to expand...
Click to collapse
That looks normal - the 'Image not signed or corrupt' message is normal as TWRP has not been cryptographically signed. As you've unlocked your bootloader that message is informational to alert that you're flashing non-Motorola files to your device (which you are).
I'd reboot to recovery after flashing and perform the other steps required (which appear to include disabling dm-verity: https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737 )

When flashing super su i get the error message
-extracting ramdisc
---failure aborting

DrunkenPanda2000 said:
When flashing super su i get the error message
-extracting ramdisc
---failure aborting
Click to expand...
Click to collapse
Flash Magisk v16.0 instead of su zip. It will work.

shad.man92 said:
Flash Magisk v16.0 instead of su zip. It will work.
Click to expand...
Click to collapse
Thx for the advice i need to act before i post sometimes.
I've done this already now i'm facing issues with the magisk nethunter module. this will be discussed in their thread.

Can i close or remove this ?

DrunkenPanda2000 said:
Can i close or remove this ?
Click to expand...
Click to collapse
Yeah sure.

Boot loader unlock
Shooting Star Max said:
Weird, that validation error is usually shown when bootloader isn't actually unlocked. Have you tried unlocking it again? Have you tried with mfastboot?
Click to expand...
Click to collapse
I have tried a same,got a bootloader and tried with fastboot,but i got error 'need to enable OEM in android settings'
.Actualy my mobile stuck with logo,once moto logo appear its gets shutdown,
Looking for your reply.

no more root

Hello, this morning I got a google pay notification that I can't make a payment.
I tried to follow the last tutorial to remove the root, but now I can no longer root my phone or even use google pay.
So I tried to flash my rom via fastboot (crosshatch-qq1a.200105.002), but I get the following error message:
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8521 KB)...
OKAY [ 0.333s]
writing 'bootloader'...
(bootloader) Flashing Pack version b1c1-0.2-5946827
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
(bootloader) Flashing partition logfs
OKAY [ 0.506s]
finished. total time: 0.840s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
sending 'radio' (71404 KB)...
OKAY [ 2.431s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_b
OKAY [ 0.457s]
finished. total time: 2.892s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
< waiting for device >
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 840814800 bytes
error: update package missing system.img
Press any key to exit...
how can i fix my phone please?

chuppito said:
Hello, this morning I got a google pay notification that I can't make a payment.
I tried to follow the last tutorial to remove the root, but now I can no longer root my phone or even use google pay.
So I tried to flash my rom via fastboot (crosshatch-qq1a.200105.002), but I get the following error message:
how can i fix my phone please?
Click to expand...
Click to collapse
Guide
Do #4 'keep data', then #9 to root.
Make sure you have the latest SDK platform-tools, there is a link in the guide.
Also, make sure the USB is not plugged in to a charging USB port.

Hi, thanks it was an adb version issue.
I had done a factory restore and attempted root without success.
I am trying to flash the factory image to test the root again.
The last factory version did not work, I put back the one I had and that worked.
Thank you
Edit : suddenly, I have a bootloop

chuppito said:
Hi, thanks it was an adb version issue.
I had done a factory restore and attempted root without success.
I am trying to flash the factory image to test the root again.
The last factory version did not work, I put back the one I had and that worked.
Thank you
Edit : suddenly, I have a bootloop
Click to expand...
Click to collapse
There's also a thread in here about how to use Gpay with root. You can search for it.

Hi, I managed to install the system cleanly then root. I followed the new google pay tutorial and couldn't make it work. Does it work for you?

Hello it works with this tutorial not with others for me
https://www.xda-developers.com/enable-quick-wallet-access-google-pay-pixel-android-10/

chuppito said:
Hi, I managed to install the system cleanly then root. I followed the new google pay tutorial and couldn't make it work. Does it work for you?
Click to expand...
Click to collapse
I have used the following method (the OP only and not all of the Magisk module stuff) since the day it was posted. I have redone it many times when moving to A10 as well as when going to various ROMs on both a P3 and PX3. GPay has never once failed me since setting it up this way.
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

XT1670 revert to stock issue

SOLVED I will make a topic about it https://forum.xda-developers.com/g5/help/how-to-revert-moto-g5-xt1670-to-stock-t4183425
Hello, how are you all over there? I here in trouble with this XT1670. I have installed several roms but now i want to go back to the official one, but it dont lock the bootloader.
Tried the following command (twice) to lock the bootloader: fastboot oem lock
And i get the following result:
Code:
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.016s]
finished. total time: 0.016s
Now i use the following command: fastboot flash boot boot.img
And the following was obtained:
Code:
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB) ...
OKAY [0.545s]
writing 'boot' ...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.747s
I have already tried several. Boot, gpt, oem with official rom. All showing the error "Security version downgrade"
I also tried Lenovo's Rescue & Smart app, but it says the SKU is wrong and doesn't recognize the mobile phone.
I don't know how to continue. I could put an official rom, but when you restart the phone the bootloader appears. It only starts when press start.
Not only does that happen. Every so often, the phone turns itself off and remains in the bootloader. And then when you start up, bug reports pop up to share with who knows what.
I do not know what to do. You are the experts.
Ty in advance