Related
This is an ATT version phone I rooted this phone a couple of days ago with TWRP. However, I had to use adb to enter fastboot as it would not go to fastboot using power/volume keys. Actually, it never shows a fastboot screen, even in adb, so it may have been going into fastboot all along and I just could not see it.
So, instead of leaving well enough alone, I RUU'ed (newest ATT version from HTC site) it to try to get fastboot to work normally (it still works, I just can't see it on screen). Now, I can't get rooted again. FWIW, I did make a backup with TWRP before RUU'ed. Regardless, there is nothing on this phone I need to keep, I just want to root it before I start using it.
Any help is greatly appreciated...
Here is my unlock sequence. Note what happens if I try to flash TWRP immediately after unlock. I have to CTRL C and Reboot phone.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash unlockt
oken unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.110s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.125s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
Now when I try to flash TWRP, I get :
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recover' (20022 KB)...
OKAY [ 1.884s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.611s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
HT445####### fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.013s
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Mr Hofs said:
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Click to expand...
Click to collapse
Same Results:
C:\s>fastboot flash recovery twrpm8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.438s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.976s
C:\s>
C:\s>fastboot flash recovery twrp30m8
error: cannot load 'twrp30m8'
C:\s>fastboot flash recovery twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.889s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.616s
C:\s>
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Mr Hofs said:
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Click to expand...
Click to collapse
Already tried that, but tried again. First below is my result before I downloaded new twrp and the second one is my result after I re-downloaded image
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.896s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.899s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>
Try the HTC_fastboot adb package. It's posted several times here on xda.
Mr Hofs said:
Try the HTC_fastboot adb package. It's posted several times here on xda.
Click to expand...
Click to collapse
Still no luck, same error (see below). This worked flawless before I flashed the latest ATT RUU.
Is it possible phone is still not unlocked or would I be getting that far if it was still locked?
Question. This phone is AT&T (more details in getvar above) but at the end of the contract, AT&T sent me code to unlock the SIM. Now, the SIM I am using is on a T-Mobile MVNO (TING). Since they SIM unlocked the phone, would I be able to and would there be any advantage/risk to trying to flash the Stock RUU for HTC unlocked/developer. It is a higher software version than the ATT version I flashed (twice).
C:\FB>htc_fastboot flash recovery twrp.img
sending 'recovery' (20022 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 3(s)
Any other ideas? I can't see bootloader screen, but it appears I can access and do all bootloader functions in adb.
I would really like to be able to eliminate locked bootloader as the issue, is there anything else I can flash or try that might let me know if bootloader is still locked. I can get results from getvar and fastboot devices.
I also have an image of the phone saved from TWRP before I flashed the RUU, but seems no way to get that image back. I am not opposed to purchasing S-off if that will for sure help me.
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
joikep said:
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
Click to expand...
Click to collapse
Already tried two previous versions
rockfordpi said:
Already tried two previous versions
Click to expand...
Click to collapse
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
rockfordpi said:
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
Click to expand...
Click to collapse
OK, we can close this one out. I did want to post my solution, just in case anyone else had a similar error.
Long Story a little bit shorter, on my HTC one M8, the error:
sending 'recovery' (11976 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Was due to a locked bootloader. Because, for some reason I can't see the bootloader on my phone, I could not see the lock status, so I was having to do EVERYTHING via ADB. The problem was, when unlocking the bootloader there is screen on the phone that asks you to confirm yes or no if you want to unlock it. I could not see that screen and the instructions I was reading left that out (It was a good assumption that if one was trying to unlock one would know to say YES. LOL). So, I was missing that step. When I found that step, even though I could not see it on screen, I just blindly pushed volume down and then power to select. At that point it unlocked and allowed me to flash twrp 3.0.
Still do not know WHY I can't see the bootloader screen. I wonder if for some reason the colors are off in my bootloader screen and all the words are the same color as the background or it is trying to redirect that output somewhere else.
but at this point I am going to live with it as trying to fix it is what got me in here in the first place.
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Someone have an idea to help me ?
Many thanks
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
Click to expand...
Click to collapse
The top post is in regards to getting signature verify fail message when flashing custom recovery. So I don't see how it's the "same problem".
Be careful about saying "same problem" without giving any specific information about your actual problem, or device details. From my experience, I've seen many dozens of times where folks say they have the "same problem" and when prompted for more info, we find there are many many differences.
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
Click to expand...
Click to collapse
Did the RUU flash successfully, or were there any error messages?
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the phone.
foosee said:
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Click to expand...
Click to collapse
This is normal and expected. You can't use adb when in bootloader. And you can't use fastboot and adb simultaneously. Meaning, when one works, the other will not work, by definition.
Fastboot = only works in bootloader fastboot mode
adb = only works within OS, or alternately will work in custom recovery TWRP
If you issue the command fastboot devices, you should find that it works.
It is also not clear what you are trying to use adb to do (what commands?).
Hey, I apologize about the new thread but I can't seem to find the answer anywhere else from here. I can NOT get this damn thing unlocked. I have went to HTCDev. Got my unlock_code.bin. Plug in the file to the fastboot directory, run the command and this happens:
C:\Users\Xyria\Desktop\htc root\fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.008s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.065s.
I've tried getting new bin files, using a different browser to download the files, everything. I've made sure that OEM Unlocking and USB Debugging are turned on.
I noticed that when I prompt for the Identifier token, this happens:
C:\Users\Tae\Desktop\htc root\fastboot>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 3E27037B17FEB4FAEDC1A20E2217CFA9
(bootloader) F96D682BECF7F1E2AC5C2AE4CC5092F2
(bootloader) ED3DEA52E0188B695B93FB1FD94465CD
(bootloader) 4F34BE816CFBEC1C783D5CAEAF2DF427
(bootloader) DA2974C3BCF133DD3F6648C56DE93DFE
(bootloader) 18D887CE6B0549A0F0E2AC1EA5F4E64C
(bootloader) A5097191BA197028D9D99E4D40E5B078
(bootloader) A6A0DE48ED0E4F7F77EEB533B2B520B2
(bootloader) D22F541EDF71EB0D7EBD9698BAE2BE68
(bootloader) CA1752D23E7DA7D8977024E93B7DE0CE
(bootloader) A70A97DE25BCAE70073CDECF3DFD6D25
(bootloader) 737A41254DE10723FA7E0558B043AC1C
(bootloader) 9A9FEB98F1C55DD167DE63B519DD1934
(bootloader) 2D203A3FF4FD71394732365ACC443794
(bootloader) D76BF85C7B23CFF7D56912AB963C97F9
(bootloader) 9679FB42A661A65AFE1B446BE19B2499
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.090s]
finished. total time: 0.090s
I'm not sure what "enable unlock" means. I am doing it from download more for sure using vol down and power. It successfully downloads the file but will not write it. This is starting to frustrate me, lol.
Nothing I'm doing is working past this point. Any ideas? I really just want to root this thing.
Have you tried rebooting back into download mode? Also just get another unlock.bin code cause sometimes the first one won't work.
Sent from my HTC 10 using Tapatalk
Try changing USB ports. You've already done everything else I would have suggested but you can also try going into settings and doing a factory reset, skipping the setup and just enabling debugging and oem unlock and starting over with a new key.
Nope, did nothing.
EtherealRemnant said:
Try changing USB ports. You've already done everything else I would have suggested but you can also try going into settings and doing a factory reset, skipping the setup and just enabling debugging and oem unlock and starting over with a new key.
Click to expand...
Click to collapse
I've reset the device 3 times now. Same error every time no matter what computer I'm on or how many unlock code bin's I get. Sigh.
explasia said:
I've reset the device 3 times now. Same error every time no matter what computer I'm on or how many unlock code bin's I get. Sigh.
Click to expand...
Click to collapse
Are you rebooting to bootloader or to download? On the 10 this has to be down in download mode to work adb reboot download then try the unlock.bin from there. Unless you've already done that I don't know what else could help
bbell101584 said:
Are you rebooting to bootloader or to download? On the 10 this has to be down in download mode to work adb reboot download then try the unlock.bin from there. Unless you've already done that I don't know what else could help
Click to expand...
Click to collapse
Right, I'm going to download mode. Thanks for your help. I'll take a shot in the dark after work and say its possibly Windows 10's fault. I'll try it on linux when I get back home.
Are you deleting the (bootloader) on each line before using the token? If not, that's your problem.
metalfan78 said:
Are you deleting the (bootloader) on each line before using the token? If not, that's your problem.
Click to expand...
Click to collapse
Yes I did. I copied only the code and the <<<>>> section.
I ran into the same issue, and I had extra 'spaces' in various spots from deleting those, after I cleaned up the token it worked. I copied and pasted it into notepad and cleaned it up and it worked.
Nvm
I fixed it; here's how.
I went to a Win 7 machine and did the same damn thing I was doing before.
Good ****, Microsoft.
Thanks for trying to help, guys.
For anyone on a Windows 8/10 computer who is still having this issue, open Command Prompt, right click on the header and go to "Properties." In the Options tab, check the box that says "Use Legacy console (requires relaunch)" and reopen command prompt.
Make sure "OEM Unlocking" is checked in Developer Options. Repeat all of your steps, and after you use the 'fastboot oem get_identifier_token' command, right click in the terminal window and select Mark. Highlight ONLY the area you're instructed to (from <<<< Identifier Token Start >>>> to <<<<< Identifier Token End >>>>>), then use CTRL + C or CTRL + X to copy and paste the token on HTC's site.
My unlock worked fine on Windows 10. But I also launched an admin command prompt to make sure it had all the access it may need.
Please, My M9 Is usually on a same boot loop situation.
When I start it it shows just this screen
Software status MODIFIED
LOCKED
S-ON
Security warning (Sometimes it disappear)
REBOOT
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
POWER DOWN
Phone not detected to use adb commands.
Please, I need this phone and I donn't have a warranty.
There is no solution to go out from this screen? There is no software to force flash or flash a dead phone.
There is no hardware tweak to bypass this situation...I don't know anything please.
Please my friends Help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
freshmike said:
I have exactly the same
Click to expand...
Click to collapse
Sadly, I have exactly the same answer. Sorry, but you're probably out of luck.
computerslayer said:
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
Click to expand...
Click to collapse
Thank you very much
Just to clarify, status modified on a non rooted, bootloader locked, s-on, never touched phone most likely means a dead nand which is unrecoverable.
Beamed in by telepathy.
my phone is S-ON unlocked .
Today my phone turn off and after stay on boot loop . When i try go to recovery mode or download mode just restart to fastboot.
I connect to computer but only what i can get after command: fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT558YJ00694
all:
I think my nand memory is F...ck ?
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
shivadow said:
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
Click to expand...
Click to collapse
I do not know if it's worth repairing on htc. Used on ebay 150 €.
freshmike said:
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
Click to expand...
Click to collapse
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
obywatel2x said:
I do not know if it's worth repairing on htc. Used on ebay 150 €.
Click to expand...
Click to collapse
Consider Swappa as well - good prices and often it's XDA users (who care more about caring for their phones) upgrading/changing phones & selling their old ones.
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
If the phone is assuredly duff then I'd try this too, even if I'm yet to know of an instance where it actually worked.. Either that or smack it one time with something really heavy. It won't fix it but you'll feel better!.
Beamed in by telepathy.
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
freshmike said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
Click to expand...
Click to collapse
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
blueberry60 said:
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
freshmike said:
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
Click to expand...
Click to collapse
Have you flashed other img files?
blueberry60 said:
Have you flashed other img files?
Click to expand...
Click to collapse
Yes, none of them went though. All command report you need to be s-off
FAILED (remote: cannot flash this partition in s-on state)
The only one which worked was hosd_signed.img, but that didn't change anything in the state of the phone.
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
freshmike said:
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Click to expand...
Click to collapse
You are in download mode?
sipas4 said:
You are in download mode?
Click to expand...
Click to collapse
Boot to bootloader (When I chose this option phone restart and come back to the same screen does nothing)
Boot to download mode (result: failed to boot to download mode press volume up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volume up or down...)
Looks like bootloader/recovery/download mode have been wiped out from the OTA update.
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.
So i brough this weird phone, and i guess i will need somebody really expert on this unlock bootloader thing this time.
0 - Locked bootloader, but in motorola software says it have root
1 - I can boot to system normaly, use sim, imeis are all ok (but there is no gapps and no way to flash it)
2 - LineageOS Pie rom
3 - i can acess fastboot (that says is locked)
4- i cannot acess recovery (when select this option, returns to fastboot)
5 - there is no "oem unlock" option in "developer options"
6 - my phone is elegible to unlock, so i already got the motorola code through the site (to use with "fastboot oem unlock CODE", but when i do the command line, says that i need to turn on the oem unlock option that doesnt exist in "developer options"
7 - If i try to boot any twrp img in fastboot mode (to flash twrp zip), the phone reboot to fastboot again (as i said, i have no acess to recovery)
8- If i update the magisk (comes with lineageOS), the system wont boot anymore, and says its corrupt, shows a recovery red window but only with "factory format" option (and if i do, the phone just format as it was in the beginning)
9 - if i try to flash anything in fastboot, i will fail coz of couse, its locked.
10- i have the box, original items, papers and documents (but its out of warranty).
11 - tried Lenovo Moto Smart Assistant, but when i put my model and awaits to fastboot, says that cannot do nothing.
I just want to use stock oreo, nothing more, is too much to ask? :crying: :crying: :crying:
Please dont ask me what the previous owner did to this phone, i dont know(he neighter, said only that after trying to install custom rom, bricked the phone, but somehow could install this lineageOS :crying: :crying:
Any help to this poor soul? Thanks already :crying: :crying:
What is the model, what does it say by the charger port? XT1789-??
In fastboot issue 'fastboot getvar all' w/o quotes and post that info here -minus your imei# that will give an idea of what firmware you need to flash to get back to stock and unlock.
41rw4lk said:
What is the model, what does it say by the charger port? XT1789-??
In fastboot issue 'fastboot getvar all' w/o quotes and post that info here -minus your imei# that will give an idea of what firmware you need to flash to get back to stock and unlock.
Click to expand...
Click to collapse
Thanks thanks for comment <3
its a XT1789-05, and the info you asked:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190608
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (4)
(bootloader) serialno: 0049486108
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 5291F1FC
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 03-22-2019
(bootloader) sku: XT1789-05
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) battery-voltage: 4051
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-19/
(bootloader) ro.build.fingerprint[1]: 02844:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.19.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: M8998_50.71.02.95R NRD
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf9e16d5 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Sat Jun 8 12:34:38 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190608
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190608
(bootloader) gitmic: MBM-3.0-nash_retail-4fc2afc-190608
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190608
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190608
(bootloader) gitrov: MBM-3.0-nash_retail-3537781-190608
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.453s
From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that.
So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there.
https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72
41rw4lk said:
From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that.
So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there.
https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72
Click to expand...
Click to collapse
Yes all works fine, sim cards, wifi, etc. But i already tried to flash stock oreo but the phone dont even allow any file flash because of locked bootloader. The pie files will bypass that? Anyways thanks thanks again to your answer, i will try what you said and follow the link (since i fix my notebook psu that screew up just now )
41rw4lk said:
From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that.
So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there.
https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72
Click to expand...
Click to collapse
not worked :crying:
did all he said : Unzip the 2 files (flashall ... and firm ...) and place them in a folder
Click on "Preparation.bat", you must generate a "flash.bat file", double click with the phone in download mode
It's all, really clean installation
It was what I did, I am not responsible for damage to your equipment
but nothing can be flashed because of bootloader locked:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.229s]
finished. total time: 0.281s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.384s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.546s
target reported max download size of 536870912 bytes
sending 'modem_a' (78412 KB)...
OKAY [ 4.390s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.417s
any more ideas ? :crying: :crying: :crying:
brunojborges said:
not worked :crying:
did all he said : Unzip the 2 files (flashall ... and firm ...) and place them in a folder
Click on "Preparation.bat", you must generate a "flash.bat file", double click with the phone in download mode
It's all, really clean installation
It was what I did, I am not responsible for damage to your equipment
but nothing can be flashed because of bootloader locked:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.229s]
finished. total time: 0.281s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.384s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.546s
target reported max download size of 536870912 bytes
sending 'modem_a' (78412 KB)...
OKAY [ 4.390s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.417s
any more ideas ? :crying: :crying: :crying:
Click to expand...
Click to collapse
well, I recommend that you download the Lenovo moto application, something like that is the name, after installing it, connect the terminal in Lenovo moto app in fastboot mode, click on the Flash option and then where it says to recover, complete the information that asks you wait for it to finish, an official ROM flashed, and from there you can start with the bootloader unlock
Have you signed into a google account on the phone? Do you see developer options in settings? I know you said you didn't see oem unlocking so that's why I ask. We'll try to tackle those and get you unlocked. It's possible that you pbl and trust zone is messed up so a blankflash might be needed to sort that.
With a locked bootloader you should able to flash the same firmware version or newer, but if your chain of trust is compromised it's a little difficult, but not impossible.
41rw4lk said:
Have you signed into a google account on the phone? Do you see developer options in settings? I know you said you didn't see oem unlocking so that's why I ask. We'll try to tackle those and get you unlocked. It's possible that you pbl and trust zone is messed up so a blankflash might be needed to sort that.
With a locked bootloader you should able to flash the same firmware version or newer, but if your chain of trust is compromised it's a little difficult, but not impossible.
Click to expand...
Click to collapse
i cant sign into google accouts because there is no gapps pre installed on LineageOS, and i cant flash anything because the bootloader locked. There is developer options but only the adb debbug option, there is no "oem unlock" option (thats why when i try to fastboot oem unlock "CODE", the prompt says that i need to first activate the "oem unlock" option into the system, but as i said, there is no OEM option inside developer options. Maybe could be this "chain of thrust" thing. What should i do? thanks
brunojborges said:
i cant sign into google accouts because there is no gapps pre installed on LineageOS, and i cant flash anything because the bootloader locked. There is developer options but only the adb debbug option, there is no "oem unlock" option (thats why when i try to fastboot oem unlock "CODE", the prompt says that i need to first activate the "oem unlock" option into the system, but as i said, there is no OEM option inside developer options. Maybe could be this "chain of thrust" thing. What should i do? thanks
Click to expand...
Click to collapse
Can you not sign into google from accounts in settings? Also, you can download the playstore apk and install it manually. Usually to enable oem unlocking you have to be signed into google. So check accounts and see if you can sign in there, and/or d/l the apk and sign in there. Reboot and check dev options again for oem unlocking once you've signed in.
Heridg said:
well, I recommend that you download the Lenovo moto application, something like that is the name, after installing it, connect the terminal in Lenovo moto app in fastboot mode, click on the Flash option and then where it says to recover, complete the information that asks you wait for it to finish, an official ROM flashed, and from there you can start with the bootloader unlock
Click to expand...
Click to collapse
i need unlock bootloader just to revert to stock. I dont want to keep unlocked, or install custom stuff. If i just had the "oem unlock" option in developer options, i could fix that. And about moto smart assistant, when i put my phone and do this steps, after choosing my phone number and model, after the program detect my phone in fastboot mode, it shows a message, "this device is not supported".
41rw4lk said:
Can you not sign into google from accounts in settings? Also, you can download the playstore apk and install it manually. Usually to enable oem unlocking you have to be signed into google. So check accounts and see if you can sign in there, and/or d/l the apk and sign in there. Reboot and check dev options again for oem unlocking once you've signed in.
Click to expand...
Click to collapse
installed both, play store and services apk's from different sites. Tried clean cache, and anything else, but there is always a message forcing to close app. Cant open them.
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
maybe isnt this messing this phone ?
Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess.
First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out.
If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.
41rw4lk said:
Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess.
First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out.
If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.
Click to expand...
Click to collapse
Please sr teach me how to do this blankflash thing, in the truth, i could bring back imeis erased from a axon 7 i had, making A LOT of crazy and dangerous moves (deleting partitions, backup binary files, editing and return back, etc), but im new with this motorola. Please teach me :crying: :crying:
41rw4lk said:
Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess.
First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out.
If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.
Click to expand...
Click to collapse
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.012s
didnt worked. I have to do this blankflash.
brunojborges said:
Please sr teach me how to do this blankflash thing, in the truth, i could bring back imeis erased from a axon 7 i had, making A LOT of crazy and dangerous moves (deleting partitions, backup binary files, editing and return back, etc), but im new with this motorola. Please teach me :crying: :crying:
Click to expand...
Click to collapse
If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of).
Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
41rw4lk said:
If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of).
Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
thanks, i will read 10x before do anytyhing, and will do carefully. i had nothing else to do. This will fix my phone or it will turn a paper weight. Im warned. Thank you sir, wish me luck and i will tell u if i have any sucess.
41rw4lk said:
If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of).
Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
if i click on .bat file:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>.\qboot.exe blank-flash
< waiting for device >
and if i do manually "fastboot oem blankflash":
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.012s
:crying: :crying: :crying: :crying: :crying: :crying: :crying:
there is any way to force hard brick and them enter in Qualcomm HS-USB QDLoader 900 mode? Maybe this way will be easier
:crying: :crying:
brunojborges said:
if i click on .bat file:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>.\qboot.exe blank-flash
< waiting for device >
and if i do manually "fastboot oem blankflash":
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.012s
:crying: :crying: :crying: :crying: :crying: :crying: :crying:
there is any way to force hard brick and them enter in Qualcomm HS-USB QDLoader 900 mode? Maybe this way will be easier
:crying: :crying:
Click to expand...
Click to collapse
boot to os, make sure adb debugging is enabled, then open a cmd prompt and enter 'adb reboot edl' w/o quotes