Related
I have a G4plus on android 7.0. I have flash few months ago this version 7.0 on my phone before the official update from moto.
My phone is rooted. Everything will work perfectly everyday except one point...
Since the begin, when i power on the phone, the boot image will be sticken on the logo Lenovo (i have flash the boot logo Lenovo instead of your device is ...).
I need to switch off, switch on several times and waiting...
If the phone will vibrate, i need to switch off again and again...
And sometimes, it will power on to the boot animation.
Because i'm not sure of the version, i will pasted the printscreen :
Build : NPJ25.75-2
Software :
{
"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"
}
Hardware :
I have free time this summer, so i want to pass using TWRP (already flash on my phone) to LineageOS or any ROM more updated...
but i want to fix this problem before !
Any idea ?
Thank you.
download stock 6.0 rom and flash using pc .
you will need to root it again after this .
then u can update officially or flash a custom rom like resurrection remix .
follow steps carefully .
Sent from my Moto G4 Plus using Tapatalk
Moto g4 plus slow charging
My moto g4 plus charging very slow campare to normal, I'm using RR ROM pls tel any one how to fix
parth00790 said:
download stock 6.0 rom and flash using pc .
you will need to root it again after this .
then u can update officially or flash a custom rom like resurrection remix .
follow steps carefully .
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Because i saw on the website, I can brick my phone... i prefer to start from a 7.0 android stock.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have relock the bootloader (if i try to upload the rom without lock, i enter in boot loop).
Keep you in touch...
In progress !
After, i want to unlock again and except skip boot loop... and flash twrp+root and migrate to lineageos after...
Always, the same problem.
In the bootloader :
- software status : modified
oem_locked (seems to be locked, OK?)
If i try to power on, i will sticked with the motorola logo (blue and M...) and vibrate, and loop, boot, logo, vibrate, loop, boot...
Again and again.
Try to flash again the rom, now with my bootloader locked.
If i tried to flash again after relock the bootloader, i will boot (with no message this device is not trusted, bad key ...)...
But after few seconds, i have a droid open with ! (red) and NO COMMAND...
What can i do please ?
At this time :
When i power on the phone :
I saw a blue screen with M logo, vibrate once ; automatic reboot.
Blue screen with M logo, vibrate once and stick on the red logo during long time (< 1 min)
Automatic reboot
and black screen with opened droid and no command written.
I will power off the phone, power on and again again ...
And sometimes, it will start to the android 7 rom (on this previous link)
Please help me
benj29 said:
If i tried to flash again after relock the bootloader, i will boot (with no message this device is not trusted, bad key ...)...
But after few seconds, i have a droid open with ! (red) and NO COMMAND...
What can i do please ?
At this time :
When i power on the phone :
I saw a blue screen with M logo, vibrate once ; automatic reboot.
Blue screen with M logo, vibrate once and stick on the red logo during long time (< 1 min)
Automatic reboot
and black screen with opened droid and no command written.
I will power off the phone, power on and again again ...
And sometimes, it will start to the android 7 rom (on this previous link)
Please help me
Click to expand...
Click to collapse
Follow this guide
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
lCrD512 said:
Follow this guide
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
This is what i already done (see my previous quote).
Thanks !
Just to be sure...
I've tried again using your link (which is the same as mine ).
But i use script batch instead of command lines...
I have downloaded the ROM.
download the script bat.
My bootloader says flashing_unlock, so i run only
To simply flash, run the "OEM Flash" file
Click to expand...
Click to collapse
At the end, the phone has rebooted with the page
"your device has been unlocked and can't be trusted
to learn more, visit : motorola.com/unlockbootloader
IT : bad key
your device will boot in 5 seconds
"
and my phone is blocked at this page....
is it normal to have bad key ?
i've try to lock again the bootloader... with the same script + lock.
EDIT : after flashing and lock again the bootloader, the phone has blue screen + red M logo.
I have waited for 1/2 minutes approx and the phone has reboot to "no-command"
Always the same problem, i don't understand !
The bad key is normal (especially with an unlocked bootloader), what's not normal is your device hanging after a flash...
Are you able to repeat the flash but executing the commands manually, please? You can copy paste each of the commands individually into your adb terminal, and check the result - it should say [OKAY] afterwards. The script, handy as it is, makes it difficult to read the outputs from each section of the flash
So the plan is:
Boot your device to the bootloader (just asking, what version is your bootloader now, B1:06?) and attach to your computer
In the adb terminal, check you're communicating with your device via 'fastboot devices', you should get a response with your device's serial number.
Open the 'OEM Flash' script in Notepad or your preferred text editor (don't run the script).
Copy each individual command line, in order, to your adb terminal and press Enter to execute that command.
EDIT - also, it's odd that on your previous flashing attempts, your device booted to the stock recovery (the opened droid with no command) rather than the system
In fact, when i saw no command, i was blocked in the recovery mode !
I tried to make a factory reset on the recovery, but the phone will do this :
- boot bluescreen, vibrate, reboot (automatic) => short time (< 15s)
- boot bluescreen => long time (1 minute) => vibrate, reboot (automatic)
- boot bluescreen, vibrate, reboot (automatic) => short time (< 15s)
- screen "no command" => recovery (power+volume up).
I try after to reboot to system...
But the phone will do the same, three reboots and recovery.
I don't understand my problem !
Thanks for your help.
After last try with lock, this is what i have on my bootloader. I will try to copy each individual command line, in order and past here the results.
BL : B1.06 (sha-0edfb0d, 2017-06-01 12:10:43)
Baseband : 8952_70030.25.03.62.01R Athene_Emea_DSDS_CUST
Product/variant : athene_16mp xt1642 32gb P2A
32 GB + 3 GB RAM
Console[Null] : null ?
Tools mode config : disabled
Battery : OK
oem_locked
software status : modified
benj29 said:
Thanks for your help.
After last try with lock, this is what i have on my bootloader. I will try to copy each individual command line, in order and past here the results.
BL : B1.06 (sha-0edfb0d, 2017-06-01 12:10:43)
Baseband : 8952_70030.25.03.62.01R Athene_Emea_DSDS_CUST
Product/variant : athene_16mp xt1642 32gb P2A
32 GB + 3 GB RAM
Console[Null] : null ?
Tools mode config : disabled
Battery : OK
oem_locked
software status : modified
Click to expand...
Click to collapse
Thanks - console [NULL] seems to be a normal response, though oem_locked means you may wish to unlock your device again before proceeding (thus, if you run into any issues, you can flash a custom ROM).
Are you unlocking by using 'fastboot oem unlock <your unlock code>' and with the OEM unlocking enabled in Developer Options?
Software status: modified might be an issue - can you remember what firmware you flashed before the soak test (the NPJ25.75-2 firmware)?
Also, as you're now on the B1:06 bootloader, try not to flash older stock firmware onto your device.
Yes, i have a problem.
Flash seems to work perfectly, see the quote after.
I start from a lock bootloader (with status modified software, how i can go back to official ?)
After the flash, the phone will start on the ROM, OK... yessss !!! NO.... if I reboot the phone i was block on the recovery again and again...
Don't understand !
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.010s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.130s]
finished. total time: 0.160s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(bootloader) committing: bootloader.default.xml ...
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.442s]
finished. total time: 0.562s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.080s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.140s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 0.373s]
finished. total time: 0.912s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.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' (16484 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.380s]
finished. total time: 0.905s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.520s]
writing 'dsp'...
OKAY [ 0.258s]
finished. total time: 0.778s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 3.045s]
writing 'oem'...
OKAY [ 7.179s]
finished. total time: 10.234s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.223s]
writing 'system'...
OKAY [ 6.132s]
finished. total time: 14.355s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250842 KB)...
OKAY [ 7.914s]
writing 'system'...
OKAY [ 5.985s]
finished. total time: 13.900s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (254485 KB)...
OKAY [ 8.018s]
writing 'system'...
OKAY [ 7.665s]
finished. total time: 15.686s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (247298 KB)...
OKAY [ 7.800s]
writing 'system'...
OKAY [ 6.589s]
finished. total time: 14.390s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (260398 KB)...
OKAY [ 8.286s]
writing 'system'...
OKAY [ 5.844s]
finished. total time: 14.134s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262041 KB)...
OKAY [ 8.247s]
writing 'system'...
OKAY [ 5.862s]
finished. total time: 14.119s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261941 KB)...
OKAY [ 8.287s]
writing 'system'...
OKAY [ 10.808s]
finished. total time: 19.096s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (82497 KB)...
OKAY [ 2.610s]
writing 'system'...
OKAY [ 1.860s]
finished. total time: 4.470s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (76954 KB)...
OKAY [ 2.428s]
writing 'modem'...
OKAY [ 1.122s]
finished. total time: 3.551s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.028s]
finished. total time: 0.028s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.030s]
finished. total time: 0.040s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (2032 KB)...
OKAY [ 0.063s]
writing 'fsg'...
OKAY [ 0.070s]
finished. total time: 0.143s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.082s]
finished. total time: 0.092s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase customize
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:customize: not found
erasing 'customize'...
OKAY [ 0.010s]
finished. total time: 0.010s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase clogo
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:clogo: not found
erasing 'clogo'...
OKAY [ 0.020s]
finished. total time: 0.024s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: -0.000s
Click to expand...
Click to collapse
echo92 said:
Thanks - console [NULL] seems to be a normal response, though oem_locked means you may wish to unlock your device again before proceeding (thus, if you run into any issues, you can flash a custom ROM).
Are you unlocking by using 'fastboot oem unlock <your unlock code>' and with the OEM unlocking enabled in Developer Options?
Software status: modified might be an issue - can you remember what firmware you flashed before the soak test (the NPJ25.75-2 firmware)?
Also, as you're now on the B1:06 bootloader, try not to flash older stock firmware onto your device.
Click to expand...
Click to collapse
Yes, i start from this Build : NPJ25.75-2.
Ok, for your remark, i don't flash older stock firmware (to prevent hard brick I supposed !)
At this time, my phone is blocked on the recovery.
Now, I unlock the bootloader using the classical method :
- phone on the bootloader (oem_locked written on the screen, software status : modified)
go on this website :
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) BLABLA0737325667#
(bootloader) BLA93232334B53465347004D6F746F2047200000#
(bootloader) BLA7E8824CF486716F8F64F4CE1E39615A649B9C#
(bootloader) BLA1B501000000000000000000000000
OKAY [ 0.129s]
finished. total time: 0.134s
Click to expand...
Click to collapse
BLA is to mask the correct code... i use the data scrub on the moto website to prevent any mistake cut/paste !
After i received the email ...
I have to run twice the commands as mark :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock MYKEY
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock MYKEY
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Bootloader is unlocked! Rebooting phone
OKAY [ 0.237s]
finished. total time: 0.240s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
And after the automatic reboot after the second command line, the phone will written on the bootloader
software status : modified
flashin_unlocked...
If i choice "start" on the bootloader, the bootpage was : "your device has been unlocked etc etc, your device will boot in 5 seconds"
and do the same thing than previous :
5 boot loops on the boot page and after 3/4 minutes will start on the motorola bluescreen and logo motorola...
Don't understand !
benj29 said:
Yes, i start from this Build : NPJ25.75-2.
Ok, for your remark, i don't flash older stock firmware (to prevent hard brick I supposed !)
At this time, my phone is blocked on the recovery.
Now, I unlock the bootloader using the classical method :
- phone on the bootloader (oem_locked written on the screen, software status : modified)
go on this website :
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
BLA is to mask the correct code... i use the data scrub on the moto website to prevent any mistake cut/paste !
After i received the email ...
I have to run twice the commands as mark :
And after the automatic reboot after the second command line, the phone will written on the bootloader
software status : modified
flashin_unlocked...
If i choice "start" on the bootloader, the bootpage was : "your device has been unlocked etc etc, your device will boot in 5 seconds"
and do the same thing than previous :
5 boot loops on the boot page and after 3/4 minutes will start on the motorola bluescreen and logo motorola...
Don't understand !
Click to expand...
Click to collapse
Hmm, that fastboot flash log and the procedure you've mentioned to unlock should work. How long are you leaving your device on the Motorola bluescreen, as after a flash/wipe it might take some time to boot?
The bootloops aren't good though, I'm wondering if the flash storage on your device is okay or if it's failing. Does your device bootloop in the bootloader or in recovery? You mentioned your device hanging whilst you were in the stock recovery?
I don't stop the phone or reboot it, i wait each time... again and again (to avoid corruption or something like this).
To be exhaustive :
1. Power on
2. Bootscreen with bad id key etc...
3. The phone will enter in boot loop (3/4 times ) and after will go in recovery with "no command".
4. enter in the recovery (power + volume up)
5. reboot to the system now from the menu
6. boot to the ROM !
I don't understand why i need to pass by the recovery...
benj29 said:
I don't stop the phone or reboot it, i wait each time... again and again (to avoid corruption or something like this).
To be exhaustive :
1. Power on
2. Bootscreen with bad id key etc...
3. The phone will enter in boot loop (3/4 times ) and after will go in recovery with "no command".
4. enter in the recovery (power + volume up)
5. reboot to the system now from the menu
6. boot to the ROM !
I don't understand why i need to pass by the recovery...
Click to expand...
Click to collapse
I'm not sure either, whether there's an issue with your system (shouldn't be, since it's a clean flash), or if that's a fallback if you get a bootloop. Are you able to boot to the home screen/setup?
Yes, sorry, i write it (my english is not good ).
Yes, after the recovery and reboot the phone using the recovery, the phone will start.
SO, at this time, I have flashed TWRP, ElementalX and root using this :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672
At this time : TWRP, root, and rom will works.
Even i need to have a complex power on sequence using the recovery
benj29 said:
Yes, sorry, i write it (my english is not good ).
Yes, after the recovery and reboot the phone using the recovery, the phone will start.
SO, at this time, I have flashed TWRP, ElementalX and root using this :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672
Click to expand...
Click to collapse
At least it's working - which root manager did you go for, phh or SuperSU or magisk?
my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
tried this too but device get recognise
Cooltango26 said:
my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:
Click to expand...
Click to collapse
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.
ADITYA_KUMAR said:
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.
Click to expand...
Click to collapse
after the official update from ....update in my device .......my device was struck in boot loop ...so i tries flashing the stock rom to repair that ....during flashing it giving the above mention error ........
Only other things I can think of is perhaps holding down your power button (for up to 2-3 minutes) to force a hard shutdown, and then try booting. Alternatively, hold down both the power and volume down key, see if you can boot into the bootloader (which it looks like you can, if you're trying to fastboot the stock ROM). If so, then try to boot into the stock recovery and try a cache wipe or a factory reset (the factory reset will obviously wipe your data).
If your device is under warranty (and you did not unlock your bootloader at any point), the service centre might be the best bet for you, as we can't do anything with a locked bootloader and you're unable to boot to get to OEM unlocking...
The new [Updated] blankflash file for Moto g4 plus [June security patch ]
Hello friends
here is the new [Updated] blankflash file for June security patch
i hope it will help you. here is complete guide https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
about how to install it.
if it's works for you please let me know:highfive:
Hey all - so weird situation - went to the EU for vacation and started noticing that the phone occasionally wants to immolate itself when roaming on EU nets . After getting back, wifi started to constantly cut out and eventually would not connect to any 5 ghz networks - all while running the phone red hot (it would return to normal temps with the wifi off). ... So I did some flashing ... which in turn resulted in everything being broken (had to rollback to stock 6.0 firmware and NON-HLOS.bin dc0ada7839303a79759f31bbd8130b3bc402ea16 sha to get cellular back) . Attempted pretty much every firmware found in this section, along with more up to date modem firmware . Current the baseband version is the one ending in SUPER_NA+ATT and so far that only results in cellular working pply . Am I banging my head against a total hardware failure here ? From the looks of it , it seems that the wifi adapter is not even being recognized ..(which is weird afaik this is software defined radio and all the wireless stuff runs off the same die) ...
some stats/versions
xt 1575
twrp 3.0
'droid 6 - nearly stock - moto_x_pure_edition_rooted_x1575_mphs24.49-18-4_v1-odexed.zip
as usual thanks for any help/advice.
Flash again these:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
@the-nozzle
dzidexx said:
Flash again these:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
@the-nozzle
Click to expand...
Click to collapse
spox - dzienki za rade - however - there are a few versions of NON-HLOS.bin floating around - which one should I use ? If you could post the sha or file size that would be awesome (i have 2 versions on hand - one is 40MB and the other 60 .. the latter one kills my cellular) . Oh also - when I fastboot flash I get a message that the modem partition was not found (or something similar) - is that a prob ? And lastly - does the twrp version matter ?
Thanks again.
Extracted from the same version:
xt1575_24.49-18-4 or from ...18-8
Download is in my signature. @the-nozzle
Nie ma za co.
so did all that :
*thenozzle**…/And/sdk/platform-tools**./fastboot flash modem ~/Downloads/android_****/NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 0.894s]
writing 'modem'...
OKAY [ 0.646s]
finished. total time: 1.540s
*thenozzle**…/And/sdk/platform-tools**./fastboot flash modem ~/Downloads/android_****/NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 0.894s]
writing 'modem'...
OKAY [ 0.645s]
finished. total time: 1.540s
*thenozzle**…/And/sdk/platform-tools**./fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.012s
*thenozzle**…/And/sdk/platform-tools**./fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.005s]
finished. total time: 0.005s
*thenozzle**…/And/sdk/platform-tools**./fastboot flash fsg ~/Downloads/android_****/fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (1356 KB)...
OKAY [ 0.030s]
writing 'fsg'...
OKAY [ 0.035s]
finished. total time: 0.065s
*thenozzle**…/And/sdk/platform-tools**./fastboot flash bluetooth ~/Downloads/android_****/BTFM.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bluetooth: not found
target reported max download size of 536870912 bytes
sending 'bluetooth' (1295 KB)...
OKAY [ 0.029s]
writing 'bluetooth'...
OKAY [ 0.027s]
finished. total time: 0.056s
... rebooted ...
... and still no love from wifi or bluetooth . Tried with 18-8 and 18-4 (sizes of the binaries are exactly the same).. I am leaning more towards a real hardware failure here ... Any further suggestions are more than welcome .
had the bootloader unlocked and ended up giving hardbrick after an update via OTA.
I managed to recover but had the alert that the bootloader was unlocked, so I wanted to block again, then by fasstboot, I made the command: fastboot flashing lock, and apois this alert began to appear.
I'm afraid to give a factory reset and give hardbrick.
image attached
https://drive.google.com/file/d/1V_UK0iGIhDO31dETqs9t83uZ_TOHHYIJ/view?usp=sharing
What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.
echo92 said:
What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.
Click to expand...
Click to collapse
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
I really wanted to reset the factory; but I'm afraid to brick it again
luis dambrowski said:
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
Click to expand...
Click to collapse
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.
echo92 said:
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.
Click to expand...
Click to collapse
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem
luis dambrowski said:
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem
Click to expand...
Click to collapse
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go... never mind, I had a look at my ADB folder and the same is for me
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)
echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Click to expand...
Click to collapse
a piece of the log
"
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.174s]
finished. total time: 0.175s
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.176s]
finished. total time: 0.178s
D:\Downloads\Nova pasta (2)\teste>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.146s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.128s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.329s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.095s
D:\Downloads\Nova pasta (2)\teste>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.176s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.194s
D:\Downloads\Nova pasta (2)\teste>fastboot flash recovery recovery.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' (16484 KB)...
OKAY [ 1.241s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.254s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.540s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.553s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 3.140s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.149s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 16.071s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.079s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250846 KB)...
......
"
echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)
Click to expand...
Click to collapse
I will do now,
D:\Downloads\Nova pasta (2)\teste>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.067s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.209s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.368s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.105s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.120s
D:\Downloads\Nova pasta (2)\teste>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.738s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.755s
D:\Downloads\Nova pasta (2)\teste>fastboot flash recovery recovery.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' (16484 KB)...
OKAY [ 0.707s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.723s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.696s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.710s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 4.547s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.555s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
luis dambrowski said:
I will do now,
.
Click to expand...
Click to collapse
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.
echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
and if I do a blankflash again now and do the rom flash, would it work?
luis dambrowski said:
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.
Click to expand...
Click to collapse
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
When I did the GPT / bootloader flash (gpt and boot) process, there was apparently no change.
do you suggest doing the flash with that (bootloader.img and gpt.bin) now? to remove this alert?
in fact this alert does not bother me, but I intend to remove it for future upgrade via OTA.
finally I will try to redo the process with ADB v1.4.3.
echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA
luis dambrowski said:
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA
Click to expand...
Click to collapse
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
ainda esta no firmware de março de 2017!
Tive uma ideia de desbloquear o bootloader e instalar o TWRP e colocar uma custom rom. No entanto, o código de desbloqueio não pode ser encontrado no site da motorola, mas sim o desbloqueio do bootloader.
Pois bem, o probloma aqui é o bootloader !!
Estou sem ideias de como prosseguir.
Sera que quando sair de novo update, (talvez algum) de certo o processo?
echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
good news!!! solved problem.
What did I do:
I used the command: fastboot flashing unlock
then he asked to repeat the command and then unlocked the bootloader, with the alert that was yellow turned red.
There I did the rom flash of April 2018 and it went without errors.
rom update and no bootloader alert.
echo92 thank you very much for your attention. big hug!!!
HI All,
I got a XT1580 from a friend and I'm trying to help him out. The phone loops on the Moto Logo or goes into Bootloader mode. Recovery seems not to work .. (shows : no command). Phone has a locked BL, when I try to use the Moto Unlock code, it says of course I need to All OEM Unlock in Android settings .. what an irony, the phone is not starting up to set this. I have installed RSD Lite, tried to flash stock rom .. fails on flashing gpt.bin.
I tried flashing manually:
Code:
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (1889 KB)...
OKAY [ 0.063s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.156s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.281s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.922s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot flash recovery recovery.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' (41040 KB)...
OKAY [ 1.264s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.929s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (256768 KB)...
OKAY [ 7.931s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.290s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (255430 KB)...
OKAY [ 7.913s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.945s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (256099 KB)...
OKAY [ 7.854s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.885s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot flash system modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
error: cannot load 'modem': No such file or directory
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot flash modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (40420 KB)...
OKAY [ 1.234s]
writing 'modem'...
OKAY [ 0.859s]
finished. total time: 2.094s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (661 KB)...
OKAY [ 0.031s]
writing 'fsg'...
OKAY [ 0.031s]
finished. total time: 0.062s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.656s]
finished. total time: 0.672s
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>reboot
'reboot' is not recognized as an internal or external command,
operable program or batch file.
D:\Incomming\platform-tools-latest-windows\platform-tools\xforce>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
Anyone any ideas? Just tying to get stock working.
freshmike said:
HI All,
I got a XT1580 from a friend and I'm trying to help him out. The phone loops on the Moto Logo or goes into Bootloader mode. Recovery seems not to work .. (shows : no command). Phone has a locked BL, when I try to use the Moto Unlock code, it says of course I need to All OEM Unlock in Android settings .. what an irony, the phone is not starting up to set this. I have installed RSD Lite, tried to flash stock rom .. fails on flashing gpt.bin.
I tried flashing manually:
Anyone any ideas? Just tying to get stock working.
Click to expand...
Click to collapse
You have to flash the same or newer firmware to the phone already has. With a locked bootloader, you need to make sure you are flashing the same or newer firmware. You will get a GPT. bin error and can brick if you're trying to flash older firmware.
So look for the last firmware that was released for this phone.
ChazzMatt said:
You have to flash the same or newer firmware to the phone already has. With a locked bootloader - - which the Droid Turbo 2 will always have - - you need to make sure you are flashing the same or newer firmware. You will get a GPT. bin error and can brick if you're trying to flash older firmware.
So look for the last firmware that was released for this phone.
Click to expand...
Click to collapse
Ok, thanks got the Andriod 7.0 EU firmware, flash with RSD was successful. Still bootloop on Moto logo Recovery menu works. Tried to reset phone, no luck.
freshmike said:
Ok, thanks got the Andriod 7.0 EU firmware, flash with RSD was successful. Still bootloop on Moto logo Recovery menu works. Tried to reset phone, no luck.
Click to expand...
Click to collapse
Sounds like you did everything correctly. I'm sorry, I'm out of ideas.