yashsingh1/xdaforums huggingface dataset:
[Moto G5 Plus Questions & Answers] santiagoeg:
hola soy de argentina y tengo el mismo problema con un g5s plus como llo solucionaste?

---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------

hola tengo el mismo problema con un moto g5s plus como hiciste para solucionarlo
[Moto G5 Plus Questions & Answers] riyan65:
Please follow XDA rules.

All threads should be in English only.

You can use Google translate to translate in English.
[Moto G5 Plus Questions & Answers] alevity:
I bricked mine installing the 67 Ota update while rooted.. But wasn't hard bricked (please define hard bricked) as I could still boot to bootloader. I used windows pc program from here the moto g5 plus toolkit flashed stock

---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------

I see your a senior member and don't mean to question you when you say hard bricked. Even if you can't get it to boot to bootloader the tool kit may still recognize it as connected
[Moto G5 Plus Questions & Answers] MarckozZ:
Well I had a Moto G, Moto G3 and this Moto G5 Plus, so I flashed things a LOT of times on the past two phones but, when I mean hard bricked here is HARD BRICKED!

No response at all, no bootloader screen or whatsoever, plus "qsusb_bulk" when plugging it to my PC: hard brick. I know that one member here made a blankfile to flash this device "potter" but it doesn't work for me... So, I'm pretty much trapped in this situation...
[Moto G5 Plus Questions & Answers] alevity:
Damn bro... Hmm.. I've been flashing since donut and I am soo grateful and probably just lucky I have never managed a hard brick.. Thought I did few times. Flashed wrong Rom as well once (luckily Samsung devices are lil easier to recover).. I have soft bricked and panic attacked myself so much over the years I seriously am starting to not want to do it anymore haha. I think we'll need to find a Motorola dev kit. Or possibly open it (not fun with this device video on youtube made me realize I won't be replacing the battery) and reset a jumper on the motherboard if that's even relevant with this device. It may have a soft fuse instead. But pretty much any hardware options are mute due to the low price of replacement....

---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------

Not suggesting anything... But a hard bricked device is kinda hard to tell you rooted.. Oem unlock does supposedly register you with moto.. But how long ago did you buy and where.. And do you have a young teenage daughter who can go in crying
[Moto G5 Plus Questions & Answers] MarckozZ:
LOL, This device has less than one month old, I unlocked the bootloader today and instantly flashed the LATAM firmware and tried the .67 OTA and it died, And no kids! So, I'm screwed! :D Great isn't it?

I'll have to save to buy another phone until some solution comes up ( [MENTION=1829889]vache[/MENTION] please help!!!)
[Moto G5 Plus Questions & Answers] Cronoss:
Did you try with the linux recovery tools?

Probaste con el script en linux?
[Moto G5 Plus Questions & Answers] MarckozZ:
No tengo una PC con dual boot y Linux por ahora... Vere si lo puedo mandar a un service.

I don't have a PC with dual boot and Linux at the moment... I'll see if I can send it to a service center.
[Moto G5 Plus Questions & Answers] Cronoss:
Proba con virtualbox que es gratis. Bajate Ubuntu y hacelo desde ahi. No es dificil. Vale la pena probar.

Try installing virtualbox which is free. Download something like Ubuntu and do it from there. It's not hard.
[Moto G5 Plus Questions & Answers] MarckozZ:
I'll try this. The thing is I don't have enough RAM to run a VirtualBox instance, So I'll have to make another partition :P
[Moto G5 Plus Questions & Answers] Tomadock:
Same thing happened to me and I'm visiting another country. What a nightmare.
[Moto G5 Plus Questions & Answers] MarckozZ:
Yea bro... I'll try to find a way to get this solved!
[Moto G5 Plus Questions & Answers] alevity:
Cheering for you all
[Moto G5 Plus Questions & Answers] itslels:
Its been a long while, but I'm pretty sure if it says qusb_bulk when you plug it into USB, then all hope isn't lost. A quick google of "qusb_bulk fix" brings up a lot of results and things to try. Maybe start here. https://www.google.com/amp/s/amp.reddit.com/r/MotoX/comments/4dt59q/qhsusb_bulk_fix/
[Moto G5 Plus Questions & Answers] MarckozZ:
Thanks for coming bro. Already tried this and it doesn't work! 'll have to live with this until devs come up with new blankflash files to revive this thing!
[Moto G5 Plus Questions & Answers] Paulo Narley:
[MENTION=5046876]MarckozZ[/MENTION]

Sorry for the bad english, I'm at fault in this but the google translator too.

Hello Friend, I went through the same situation as you with the .67 update. Although I unlocked the bootloader and invalidated the warranty, I decided to take it to the assistance of the motorola, because I believe that its technicians are trained and because it is a local representative of the motorola, they are also honest ... just to hear from them that I needed to change the Plate and the cost for this is half a new here in Brazil. But after much research, I was convinced that it was not the card, so I opened the device and gave a shock to the battery, do not ask me why I did this, probably the desperation made me do it, but it did not help, the device continued unplugged , It just blinked the led when it was connected and was identified by the PC device manager, so I gave up for a while.

But as I was not happy using my motoE1 I decided to try one more time, it was when I came across this post:

Https://xdaforums.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

And tried using the blankflash made available by vache for the potter but did not succeed in any of the countless attempts.

So I concluded that the .67 update should have been upgraded and so it was not possible to go back with the blankflash, but browsing through the tree of vache folders I saw that it had also available for the albus (MotoZ2Play) and I decided to take a risk, and because there A certain similarity between the two devices and this latest one worked out. I know I will be criticized for recommending this to you, but it was the only solution I got, but I can not fail to mention that after doing that things will not be the same anymore.

After having success with the tutorial of the above link using the blankflash of MotoZ2play that you can find here

Http://cloud.vache-android.com/Moto/albus/blankflash/

You have to use bootloader, gpt and addison recovery (MotoZplay)

Https://drive.google.com/open?id=0B7X6bQHmiX_BY29Damx5ejEyX1U

To return to stock rom.

It's important to do this right after the blankflash tutorial here:

Https://xdaforums.com/showpost.php?p=71405834&postcount=23

Once this is done you can use the Moto.G5.Toolkit available here

Https://xdaforums.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203

To install NPN25.137-33 / 35, but do not forget to replace bootloader, gpt and recovery in the firmware folder.

Remember, that was the decision I made, so do it at your own risk, although the risk here is to bring it back, I do not know what it will be with future updates.

Good luck!
[Moto G5 Plus Questions & Answers] MarckozZ:
IT WORKED!!!!

Well at least partially... I can enter bootloader now but, when I flash the firmware (using gpt, bootloader and recovery you gave) it only starts and shows the unlocked bootloader warning and restarts... So, it turns on now but I cant pass that warning screen.

Any suggestions?

What I did was this:

*blankflashed the albus files

*flashed the entire firmware (from US, 135-35)

Restarted but got a bootloop.. then..

*reflashed firmware but replacing bootloader, gpt and recovery from Z play (forgot to do this the first time :( )..

and still have a bootloop on the warning screen... am I missing something? Did you phone instantly rebooted as usual?

SO, basically what I will have is a Moto G5 Plus with Moto Z Play bootloader, GPT and recovery..
[Moto G5 Plus Questions & Answers] alevity:
Super exciting that it's at least getting a boot loaded now.. I wondered if by any chance the issue now is that your trying to flash a stock rom that is a downgrade from the updated 67.. If it even recognized the update before bricking
[Moto G5 Plus Questions & Answers] MarckozZ:
I sideloaded the OTA via adb, and the recovery flashed it without any problems at that moment... So it had the .67 update installed but also a corrupted bootloader.

Now, it doesn't have the .67 update anymore since i flashed the 135.35 US firmware. So the system has the 135.35 version, but with the recovery, partition table and bootloader from Moto Z Play.

After I push the power button it shows the warrning screen and either stays there, bootloops or shows a recovery screen with the circle animation with the word "Erasing" beneath, and then bootloop again.

My guess is that bootloader searchs for a suitable Moto Z Play firmware and, since it has another, it won't boot at all.

Also I'm worried now. Since this phone now has software parts fron another Moto phone, I wonder if I will be able to flash gpt.bin and bootloader.img from the upcoming O firmware. I'll die if now I'm only able to flash things from Moto Z Play instead of potter..
[Moto G5 Plus Questions & Answers] Paulo Narley:
:fingers-crossed:

After the albus blankflash you need to install the bootloader and gpt and reboot to the bootloader, then replace in the firmware folder NPN25.137-33 or 35 the bootloader gpt and recovery and then install all the firmware stock using the method you I recommend using Moto.G5.Toolkit to make everything easier, I have re-done the process of installing update .67 only to confirm that I would have the same problem and these steps helped me to solve it again.
[Moto G5 Plus Questions & Answers] Cronoss:
This is obvious at this point, but pressing volume down + power does nothing? just shows the warning screen and loops?
[Moto G5 Plus Questions & Answers] tushar.gupta224:
Plz help broooo
[Moto G5 Plus Questions & Answers] Rakesh1b:
bro use the files of albus blankflash and http://cloud.vache-android.com/Moto/potter/blankflash/

drive.google.com/file/d/0B7X6bQHmiX_BY29Damx5ejEyX1U addison partition and bootloader,recovery

stock rom https://xdaforums.com/g5-plus/development/stock-debloated-deodexed-t3619972

bro atleast search all the pages of this thread

why simply asking please you can search no?
[Moto G5 Plus Questions & Answers] tushar.gupta224:
I go through all the thread but blank flash files are not working for me

**** Log buffer [000001] 2018-04-01_18:47:56 ****

[ 0.002] Opening device: \\.\COM4

[ 0.016] Detecting device

[ 0.018] ...cpu.id = 70 (0x46)

[ 0.019] ...cpu.sn = 92328227 (0x580d123)

[ 0.019] Opening singleimage

[ 0.020] Loading package

[ 0.022] ...filename = singleimage.pkg.xml

[ 0.024] Loading programmer

[ 0.024] ...filename = programmer.mbn

[ 0.024] Sending programmer

[ 0.235] Handling things over to programmer

[ 0.236] Identifying CPU version

[ 0.238] Waiting for firehose to get ready

[ 60.722] Waiting for firehose to get ready

[120.808] ...MSM8953 unknown

[120.808] Determining target secure state

[120.810] Waiting for firehose to get ready

[180.902] ...secure = no

[180.915] Waiting for firehose to get ready

[241.002] Configuring device...

[241.005] Waiting for firehose to get ready

[301.099] Waiting for firehose to get ready

[361.191] Waiting for firehose to get ready

[421.282] Waiting for firehose to get ready

[481.376] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

[481.376] Check qboot_log.txt for more details

[481.377] Total time: 481.400s

[481.419]

[481.419] qboot version 3.40

[481.419]

[481.419] DEVICE {

[481.419] name = "\\.\COM4",

[481.419] flags = "0x64",

[481.419] addr = "0x61FE5C",

[481.419] sahara.current_mode = "0",

[481.419] api.buffer = "0x3304020",

[481.419] cpu.serial = "92328227",

[481.419] cpu.id = "70",

[481.419] cpu.sv_sbl = "0",

[481.419] cpu.name = "MSM8953",

[481.419] storage.type = "eMMC",

[481.419] sahara.programmer = "programmer.mbn",

[481.419] module.firehose = "0x2FB8CE8",

[481.419] cpu.ver = "0",

[481.419] cpu.vername = "unknown",

[481.419] api.bnr = "0x2E68410",

[481.419] }

[481.419]

[481.419]

[481.419] Backup & Restore {

[481.419] num_entries = 0,

[481.419] restoring = "false",

[481.419] backup_error = "not started",

[481.419] restore_error = "not started",

[481.419] }

[481.419]

my phone is booting in bootloader..........
[Moto G5 Plus Questions & Answers] praveen Glaxi:
Dude i had the same issue but now .... if u have windows 10 disable drivers enforcement and then perform blanks flash step
[Moto G5 Plus Questions & Answers] tushar.gupta224:
Still didn't working brooo.....
[Moto G5 Plus Questions & Answers] ajthekiller:
**** Log buffer [000001] 2018-04-03_09:26:04 **** [ -0.000] Opening device: \\.\COM8

bro opening error please help me :crying::crying::crying::crying::crying::crying::crying:

i tried both vache and albus please help me

**** Log buffer [000001] 2018-04-03_09:26:04 ****

[ -0.000] Opening device: \\.\COM8

[ -0.000] ERROR: device_open()->error opening device

[ -0.000] Check qboot_log.txt for more details

[ -0.000] Total time: -0.000s

[ -0.000]

[ -0.000] qboot version 3.40

[ -0.000]

[ -0.000] DEVICE {

[ -0.000] name = "\\.\COM8",

[ -0.000] flags = "0x60",

[ -0.000] addr = "0x28FE6C",

[ -0.000] api.bnr = "0x332E40",

[ -0.000] }

[ -0.000]

[ -0.000]

[ -0.000] Backup & Restore {

[ -0.000] num_entries = 0,

[ -0.000] restoring = "false",

[ -0.000] backup_error = "not started",

[ -0.000] restore_error = "not started",

[ -0.000] }

[ -0.000]

---------- Post added at 04:09 AM ---------- Previous post was at 04:05 AM ----------

here are the logs ::crying::crying::crying::crying::crying::crying:

**** Log buffer [000001] 2018-04-03_09:26:04 ****

[ -0.000] Opening device: \\.\COM8

[ -0.000] ERROR: device_open()->error opening device

[ -0.000] Check qboot_log.txt for more details

[ -0.000] Total time: -0.000s

[ -0.000]

[ -0.000] qboot version 3.40

[ -0.000]

[ -0.000] DEVICE {

[ -0.000] name = "\\.\COM8",

[ -0.000] flags = "0x60",

[ -0.000] addr = "0x28FE6C",

[ -0.000] api.bnr = "0x332E40",

[ -0.000] }

[ -0.000]

[ -0.000]

[ -0.000] Backup & Restore {

[ -0.000] num_entries = 0,

[ -0.000] restoring = "false",

[ -0.000] backup_error = "not started",

[ -0.000] restore_error = "not started",

[ -0.000] }

[ -0.000]

---------- Post added at 04:13 AM ---------- Previous post was at 04:09 AM ----------

some help me please i am from india my device has bricked moto g5 plus

i tried to blank flash but it give only one error : please help :crying::crying::crying::crying::crying::crying::(:(:(:(

**** Log buffer [000001] 2018-04-03_09:26:04 ****

[ -0.000] Opening device: \\.\COM8

[ -0.000] ERROR: device_open()->error opening device

[ -0.000] Check qboot_log.txt for more details

[ -0.000] Total time: -0.000s

[ -0.000]

[ -0.000] qboot version 3.40

[ -0.000]

[ -0.000] DEVICE {

[ -0.000] name = "\\.\COM8",

[ -0.000] flags = "0x60",

[ -0.000] addr = "0x28FE6C",

[ -0.000] api.bnr = "0x332E40",

[ -0.000] }

[ -0.000]

[ -0.000]

[ -0.000] Backup & Restore {

[ -0.000] num_entries = 0,

[ -0.000] restoring = "false",

[ -0.000] backup_error = "not started",

[ -0.000] restore_error = "not started",

[ -0.000] }

[ -0.000]
[Moto G5 Plus Questions & Answers] Sagazdelrey:
Tried it on g5s plus xt1806

I bricked my moto g5s plus xt1806 and as my pc detected as HS USB QDLOADER 90008 and wasn't finding any other options I went and tried albus blank flash. It did flash but doesn't start in any way and my pc doesn't recognise it at all.

Am I screwed?
[Moto G5 Plus Questions & Answers] echo92:
Try unplugging your device and reconnecting it to your computer. Perhaps that may load the correct drivers (though verify that you have Motorola drivers, ADB/fastboot drivers installed and you have driver signature enforcement disabled if running Windows 10 or 8.1).

Did you see from the blankflash output if the blankflash had worked? Do you still have the log?

However, looking through your previous posts, it does begin to suggest your device hardware is failing - however, with an unlocked bootloader, you have no Motorola warranty (though your local consumer laws may still protect you).
[Moto G5 Plus Questions & Answers] Sagazdelrey:
Thanks for your reply! I did unplug, and reconect it at the moment with nothing happening. I had previously downloaded Motorola drivers and ADB/fastboot. I had entered testing mode for the process (think that disables driver signature enforcement) but I had installed my drivers before that, would that have caused a problem?

I'm stupid as I didn't save the log (after panicking and not finding what to do I disabled test mode and rebooted my pc), and I don't recall exactly what it said but I thought it did flash. Though on second thought, if worked it should started the bootloader, sholdn't it?

Luckily now, out of test mode, my pc once again recognizes it as HS USB QDLOADER 9008.

I don't expect you to spoon feed me but after two days investigating I'm still lost and you are the first to extend a hand.

I you would take a moment to read my post describing everything that happened and share any thought you have on it I would inmensly appreciate it!

https://xdaforums.com/moto-g5s-plus/help/device-hardbricked-kindda-t3787637

Thanks again!!

Is there anyway I can know for sure? I don't recall gettin it hit for at least a week before it failed and that was with a protectve case on, however it has had a share of unprotected falls couple months back.

Thing is Lenovo claims warranty only extend to the country you bought it in. I live in Argentina and bought it to a guy that brought it from USA. Don't know if that grants me any sort of warranty. And even if it did, wouldn't fall damage make it null?
[Moto G5 Plus Questions & Answers] echo92:
If memory serves me, there may be a blankflash log in the blankflash folder (next to the qboot.exe and the singleimage.bin). Open that in a text editor and see if it's the output. But yes, the blankflash should auto-reboot if the flash worked. As for installing the drivers before disabling driver enforcement, I'm not sure if it matters. However, you could force install the drivers if your device isn't recognised.

However, the symptoms you described (random reboots, startup failures, sometimes working) do suggest either firmware corruption or failing hardware (e.g. failing flash memory or the flash controller, which may explain the partition table failure (GPT). Without being able to load a GPT, a device has no idea of the layout of the flash memory, and as such has no idea where the key partitions to load - system, kernel and so forth, are).

If you can get your device into HS-USB 9008 mode, it might be worth seeing if the blankflash could run and if it does, you may wish to try flashing the latest stock firmware onto your device. I'm not familiar with G5S firmware, so you may have to consult other XDA members or firmware.center for the latest firmware https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ (be aware that firmware.center uses a cryptominer to fund itself, so don't keep the page open too long else you'll keep using 100 % CPU).

As for warranty, the Motorola warranty is void as soon as you request the unlock key. However, the device was likely already without guarantee as the warranty is non-transferable from the original owner. Furthermore, Motorola likely won't guarantee devices imported from another country (unfortunately). I'm not sure what Argentina consumer laws regarding consumer electronics are, though I'm hoping there's a provision that electronics are repairable at minimal cost to the consumer in a certain timeframe. Else, if you're unable to get the device to boot, it may require an expensive motherboard replacement (if the service centre/repair shop can even source a suitable motherboard). In that case, you may have to consider a new device.
[Moto G5 Plus Questions & Answers] Sagazdelrey:
Couldn't find a blankflash log but did a qboot log (don't know if they are the same)

It shows evey log that I know that failed

The last of them being this

**** Log buffer [000001] 2018-05-09_19:27:54 ****

[ -0.000] Opening device: \\.\COM3
[ -0.000] Detecting device
[ 4.035] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.035] Check qboot_log.txt for more details
[ 4.035] Total time: 4.035s
[ 4.035]
[ 4.035] qboot version 3.40
[ 4.035]
[ 4.035] DEVICE {
[ 4.035] name = "\\.\COM3",
[ 4.035] flags = "0x64",
[ 4.035] addr = "0x61FE5C",
[ 4.035] api.bnr = "0x2F22BC0",
[ 4.035] }
[ 4.035]
[ 4.035]
[ 4.035] Backup & Restore {
[ 4.035] num_entries = 0,
[ 4.035] restoring = "false",
[ 4.035] backup_error = "not started",
[ 4.035] restore_error = "not started",
[ 4.035] }
[ 4.035]

It's exactly like every other log saved (api.bnr varies a little between logs, repeats once the same presented here).

And I'm almost certain it's isn't the last one I saw (the one I thought that worked and that made my phone no longer recognizable by my pc).

Tomorrow I'll see what I can do about the blankflash as I can't for what's left of the day here (if it's a firmware issue, that should solve it. Shouldn't it?).

I have a doubt though.

From what I gather no one got a stock rom after doing this blankflash.

Shouldn't I go for one of the firmwares listed here instead of the lastest sanders? (Which I think is stock rom for g5s plus? I may be mistaken)

I've been rereading every post in this thread and with a bit more knowledge it seems a tad less frightining.

I guess that, given the g5 plus and g5s plus have the same processor, this solution should work for me, shouldn't it? Provided I don't have a hardware problem, I mean.

I can't express with words how much better it feels at least getting someone answering you, man.

You are like a light house in a dark tempest
[Moto G5 Plus Questions & Answers] echo92:
Thanks for that log. The sahara error suggests the blankflash couldn't establish a connection (the sahara protocol, as I understand it, communicates with the bootloader if in HS-USB 9008 mode). Sometimes that can be resolved by using the blankflash several times, they seem to be inconsistent on use (then again, for internal development tools, perhaps not surprising).

Hopefully the blankflash did work and flashed a new bootloader to your device, else firmware won't flash (stock firmware requires a working bootloader to have an active fastboot to flash). Yes - you need sanders firmware since you have a G5S Plus - G5 Plus stock firmware doesn't appear to work (and I saw a few instances of users attempting to accidentally flash potter firmware on sanders devices...). If I recall, sanders firmware was on Android 7.1.1, whereas potter firmware is on 7.0, so that's one reason it won't flash. As I mentioned before, I'm not that familiar with sanders firmware builds, though it looks like there are a few variants around, so you may have to ask in the G5S Plus forums for applicable firmware.

If stock firmware doesn't flash because of the albus Moto Z2 bootloader, which is likely, but you have a working bootloader, then if your device bootloader is unlocked still, then I would try flashing TWRP and a custom ROM or a G5S Plus TWRP flashable of the stock firmware. TWRP flashables and custom ROMs should not care about the bootloader version and a TWRP flashable of the stock ROM will be pretty close to the stock experience, just no OTA updates. Again, provided it just is a firmware error and not a hardware fault... But least you have options.