AP Fastboot Flash Mode (Secure)

[stefanhanz]

Hi there,

I tried to update my Moto G4 Plus and I think I made some big mistakes..

I can only start into Bootloader with the following text shown below:

AP Fastboot Flash Mode (Secure)
BL: B0.0E (sha-4986429, 2016-104-13 14:23:47)
Baseband: [bla] ATHENE_EMEA_DSDS_CUST
Product/Variant: athene_16mp XT1642 16GB P2A
Serial Number: [bla]
CPU: MSM8952
eMMC: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=5f
Console [NULL]: null
Battery OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected

- No TWRP or other Recovery
- No OS
- No Fastboot connection to my Win10 64bit anymore (

I think the problem is the "AP Fastboot Flash Mode (Secure)" Mode.

Any ideas how to solve it?!

thanks alot anyway

 

[rajatgupta1998]

The AP Fastboot Flash mode(secure) seems okay to me. However it is highly possible that your drivers aren't installed on the phone. So in this case try to first connect the phone to the computer and see if it get's detected or not, and then you should manually install the fastboot USB driver. Download the driver zip from Google's repository and extract it, later choose the .inf file and then the Android Bootloader Interface.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip

PS: This driver and the fastboot adb binaries are completely different thing. fastboot won't work unless you have this USB driver.

 

[stefanhanz]

Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.

I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

But I get the same message in cmd as always. < waiting for device > I dont know what to do..

edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!

Tanks alot!

Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".

Do I have to install anything else like a boot.img? I made a full wipe..

Can I use the ElementalX Kernel?

 

[echo92]

Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.

I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

But I get the same message in cmd as always. < waiting for device > I dont know what to do..

edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!

Tanks alot!

Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".

Do I have to install anything else like a boot.img? I made a full wipe..

Can I use the ElementalX Kernel?

The latest stock ROM is the NPJS25.93-14-10 (Sept 2017 security patch) build https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

You'll have to flash the stock ROM in fastboot, which would wipe TWRP off your device again. You cannot properly flash stock firmware in TWRP (only can flash the system in TWRP).

Once you've flashed the stock ROM and TWRP, you can use ElementalX, I'm using the 1.0.4 stock version on the NPJS25.93-14-10 build with magisk 13.3 (to root) and it's running stably on my XT1642.

 

[stefanhanz]

Thank you! Now its working as it should with the newest updates!

Thread can be closed. Thanks

 

[sersrendon]

Thank you! Now its working as it should with the newest updates!

Thread can be closed. Thanks

Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led

 

[Rog Ballester]

Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led

Does anyone know what happened?
I updated the rom appeared this message.

Cell Phone: Moto g 4

Please help me :crying: :crying:

Imagens:

h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV

 

[echo92]

Does anyone know what happened?
I updated the rom appeared this message.

Cell Phone: Moto g 4

Please help me :crying: :crying:

Imagens:

h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV

Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.

You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.

 

[Rog Ballester]

Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.

You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.

Não estou conseguindo, de uma olhada nessas imagens por favor

https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV

 

[echo92]

Não estou conseguindo, de uma olhada nessas imagens por favor

https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV

1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.

Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573

 

[Rog Ballester]

1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.

Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573

When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:

 

[echo92]

When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:

Can I ask how you're flashing the firmware?

Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?

I'd like to see a copy of the flashing output if possible please

 

[Rog Ballester]

Can I ask how you're flashing the firmware?

Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?

I'd like to see a copy of the flashing output if possible please

Yes, I have the room files.
Yes, my computer recognizes

I had the bootloader unlocked, I went to update and it caught


please look at the pictures:

https://goo.gl/q7AHhL

https://goo.gl/QstpTS

https://goo.gl/JSz8r2

 

[echo92]

Yes, I have the room files.
Yes, my computer recognizes

I had the bootloader unlocked, I went to update and it caught


please look at the pictures:

https://goo.gl/q7AHhL

https://goo.gl/QstpTS

https://goo.gl/JSz8r2

Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?

Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.

 

[Rog Ballester]

Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?

Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.

https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater

Do you believe you can recover your cell phone?

 

[echo92]

https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater

Do you believe you can recover your cell phone?

I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.

Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.

I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.

 

[Rog Ballester]

I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.

Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.

I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.

https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater

I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:

 

[echo92]

https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater

I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:

You're welcome

Please, in future, avoid downgrading your stock firmware if you can. If you do downgrade stock firmware, avoid OTA updates. Custom ROMs do not appear to matter in this regard.

I do not know if blankflashes will keep working as Motorola keeps updating the stock firmware. We may eventually need a new blankflash. Blankflashes are also rare as Motorola does not formally release them (luckily, we have a working one). So, do not rely on a blankflash to always bail you out of trouble.

 

[ILLUSORYINK]

Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.

I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

But I get the same message in cmd as always. < waiting for device > I dont know what to do..

edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!

Tanks alot!

Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".

Do I have to install anything else like a boot.img? I made a full wipe..

Can I use the ElementalX Kernel?

How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!

 

[echo92]

How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!

How did you get into this state in the first place?

I see from your other post you installed AICP, so you must have TWRP on your device already?

If you need to re-flash TWRP, then boot your device to the bootloader.
Connect your device to your computer, preferably with the original USB cable.
Open the ADB terminal on your computer, and ensure you have the TWRP flashable image on your computer, in your ADB folder.
In the ADB terminal, type 'fastboot devices' without quotes, ensure you get a serial number response from your device.
If you get a response, then type 'fastboot flash recovery <name of TWRP image>' without quotes, where the <name of TWRP image> is the TWRP image file name as on your computer. Ensure the file name is the same, taking into account file name extensions.
You should have flashed TWRP to your recovery partition on your device - use the volume keys on your device to select 'Recovery' then press the power button to boot to recovery. You should be booting to TWRP recovery.

In there, you should be able to copy a custom ROM and flash that within TWRP. Alternatively, you could download a fastboot stock ROM and flash that within fastboot (not TWRP) to restore your device, but ensure it's the correct and latest stock ROM for your device.