Develop Bugs

How to relock bootloader?

Hello! I need to get my E975 back on warranty, what is the way to relock bootloader again?

Install Kdz..
Sent from my LG-E975 using Tapatalk

Avantu said:
Hello! I need to get my E975 back on warranty, what is the way to relock bootloader again?
Click to expand...
Click to collapse
Your answer is in FAQ #3 go here

dalmm said:
Install Kdz..
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
You mean i can use KDZ Flasher in Fastboot mode?
sunyakram said:
Your answer is in FAQ #3 go here
Click to expand...
Click to collapse
There are 3 options, but aren't they for other Optimus versions than E975? Which do you prefer?

The thing is i can't go download mode cause i already have unlocked bootloader and it gets me to fastboot mode. I unlocked it with Freegee but the backup is gone. Is there any possibility to lock bootloader? The phone is fully working, only thing is yellow tints on screen and i wanted to get it back on warranty.

Avantu said:
You mean i can use KDZ Flasher in Fastboot mode?
There are 3 options, but aren't they for other Optimus versions than E975? Which do you prefer?
Click to expand...
Click to collapse
1st why you returning it back? 2nd i don't know too much about veriant compatibility so its batter to post there if you cant find satisfied solution here
---------- Post added at 09:27 PM ---------- Previous post was at 09:22 PM ----------
Avantu said:
The thing is i can't go download mode cause i already have unlocked bootloader and it gets me to fastboot mode. I unlocked it with Freegee but the backup is gone. Is there any possibility to lock bootloader? The phone is fully working, only thing is yellow tints on screen and i wanted to get it back on warranty.
Click to expand...
Click to collapse
I read somewhere about these yellow tints are not a big issue thay appear and disappears after some days without any repairing, (correct me if i am wrong)

sunyakram;48385401[COLOR="Silver" said:
---------- Post added at 09:27 PM ---------- Previous post was at 09:22 PM ----------
[/COLOR]
I read somewhere about these yellow tints are not a big issue thay appear and disappears after some days without any repairing, (correct me if i am wrong)
Click to expand...
Click to collapse
It can be true. I bought it used in my country from some shop. I think they have replaced the screen with new one. I talked with the shop owner and he told me that he checked the screen before sending me and it was ok, but if i want i can send them phone back so they will replace it with new one(but he didn't tell me that it was replaced already at all). But now i'm in trouble and i don't know if i can lock bootloader without EFS Backup :/ If u have any ideas, tell me please.

Avantu said:
It can be true. I bought it used in my country from some shop. I think they have replaced the screen with new one. I talked with the shop owner and he told me that he checked the screen before sending me and it was ok, but if i want i can send them phone back so they will replace it with new one(but he didn't tell me that it was replaced already at all). But now i'm in trouble and i don't know if i can lock bootloader without EFS Backup :/ If u have any ideas, tell me please.
Click to expand...
Click to collapse
If you bought it from shop so don't worry about unlocked.unlocking doesn't effect screen.

sunyakram said:
If you bought it from shop so don't worry about unlocked.unlocking doesn't effect screen.
Click to expand...
Click to collapse
Maybe, but he wrote on his warantee card that changing firmware void the warantee. So if i send him the phone back, i don't think he will want to replace screen with new one(which is quite expenisve) when he will see europe open firmware(i had brand before) with bootloader unlocked... i will just lost money sending him phone.
About yellow tints, i heard that iphones had similar problem, it was caused by glue between screen and digitizer or somewhere else, and tints disappeared after few days of using, but i can't tell if my LG will be the same.

use kdz updater and that's it. flash the original firmware the phone came with.it takes 5 minutes.

playis but
Avantu said:
The thing is i can't go download mode cause i already have unlocked bootloader and it gets me to fastboot mode. I unlocked it with Freegee but the backup is gone. Is there any possibility to lock bootloader? The phone is fully working, only thing is yellow tints on screen and i wanted to get it back on warranty.
Click to expand...
Click to collapse
Very strange! After using freege for unlocking bootloader and flashing CWM Recovery, I got a Kernel error. I tried to flash KDZ in download mode, but after start flashing process my phone reboot in fastboot. Are you in the same situation?

If u can get into recovery mode, you can flash any working ROM and then try the old version of freegee to avoid kernel errors. The update version from playstore gives this kernel error, since it flashes the bootloader of nexus4. But I think, the playstore version should be fixed by now... better to check it... search for the old version of freegee posted by davevinci...

Lol guys i'm very stupid... you can go into download mode by holding volume + and - and starting the phone. Then you can reflash it with stock firmware in LG Support Tool under emergency options or something like that(i'm not using english version so i don't know how it sounds in english) or with KDZ Updater. Ofc my phone is fully working, all i want is to get back to stock settings.

You already had the answer...use the damn kdz updater to flash stock firmware,then perform a hard reset. end of story. why the drama??why do you guys don't read the whole story?why don't you learn how to revert the changes you make BEFORE starting doing them?

Recover on from bootloop on H815 EU

Hi guys,
Yesterday I got sweaty hand palms.
My EU 815 G4 is unlocked, the official way, and I had rooted it.
Then I tried to install xposed from twrp and I did something wrong, and ended up in bootloop...
I have just updated to v20b before, and forgot to connect the phone to the PC, and allow the PC debug access before installing xposed, so i could see the phone in ADB mode, but couldn't access it.
Of course I hadn't made a backup before this - I like to cry
Just as a desperate try, when everything else had failed, i thought about using the new tool provided by shakeyabooti LG UP to flash the factory KDZ all over
I put the phone in SW. update mode by:
1. Turning off the phone
2. connecting USB cable to the PC
3. Press and hold vol. up while connecting the USB cable to the phone
Then i downloaded the v20b KDZ file, provided by Autoprime (since this was what i where allready running)
Opened LG UP, loaded the H81520B_00.kdz, marked REFURBISH
Lastly i pressed "Start" and waited for about 15-20 minutes and "TADAAAA"
The phone where up and running again... only things lost where root and TWRP
- Sharing since I'm properly not the only one ending up in this kind of mess :laugh:

Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?

rakinisbat said:
Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?
Click to expand...
Click to collapse
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help

Follow_and_Feel said:
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help
Click to expand...
Click to collapse
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.

rakinisbat said:
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.
Click to expand...
Click to collapse
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious

Follow_and_Feel said:
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious
Click to expand...
Click to collapse
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG

rakinisbat said:
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG
Click to expand...
Click to collapse
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?

Follow_and_Feel said:
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?
Click to expand...
Click to collapse
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.

rakinisbat said:
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.
Click to expand...
Click to collapse
Haha! I can completely subscribe to the flash-a-holic :laugh: Well ok. So it's even worse than i thought Sorry for ya. At least you live on a continent everyone here desires to go to :laugh: Going to Australia is very popular in germany But sorry that you're experiencing trouble with your LG. Good luck with that nexus - it's an awesome phone, too. Bye bye

I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue

zwodziarz said:
I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue
Click to expand...
Click to collapse
Hi sir
I decide to buy lg g4.
If i flash cm ,bootloop not happend again?
Thank you

It doesn't matter what firmware you have got. Bootloop is happening because of hardware failure.
Odesláno z mého LG-H815 pomocí Tapatalk

Nexus 5x stuck at google screen [Potentially Hard-bricked]

*** The issue is resolved!!! Thanks to xda, the solution is provided in the link in the comments.***
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for their help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys . :good:
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Will replacing the motherboard get my phone back? Any kind of suggestion will be very much appreciated.

Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...

Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766

what is your model H790 or H791
16 or 32 GB?

DC_Knight said:
Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...
Click to expand...
Click to collapse
Well, I don't get bootloops, my phone is just stuck at the Google screen and I can enter recovery mode (lying Android with red exclamation mark), from there I can enter Android recovery mode, where ADB sideload is available.
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
Like I mentioned in point 5, I did exactly that as mentioned in this link.
Duckscreen said:
what is your model H790 or H791
16 or 32 GB?
Click to expand...
Click to collapse
It's H791, 32 GB.

There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??

jadu45 said:
There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??
Click to expand...
Click to collapse
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk

EeZeEpEe said:
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...

jadu45 said:
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...
Click to expand...
Click to collapse
Ah my bad. TL;DR on my end.
Sent from my Nexus 5X using Tapatalk

Please say something about replacing the motherboard. It's very very pricey, so I want to be sure -_-

sounds like its hardware problem, contact seller to replace it. if not going to happen, then buy a new phone from a company that does have a dealer in your country to warrant. aside of camera, the specs of other phones at this price range are better

That thought is also roaming around my head, still Nexus is Nexus!

What's the price going for the 5X over there? It's as low as $280 here in the US which is easy better then it's original.
Sent from my Nexus 5X using Tapatalk

Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.

questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Thanks for this, it looks interesting and I definitely didn't try that. I'm at office right now, I'll let you know after trying this.

harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!

jadu45 said:
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!
Click to expand...
Click to collapse
Goodluck, and let us know the result.. :fingers-crossed:

A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.

ShishkaBerry said:
A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.
Click to expand...
Click to collapse
Well, there is no authorized dealer here; I had to buy it from a local shop. So, there is no warranty!

harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Both of you provided me the link. I don't know who you are, but I if I find you you guys are going to have a treat for sure. I literally cried when I got my phone back. Thank you guys. Thanks xda!

Help [hardbricked device] urgent need of help asap

Ok so i was just rooting when my phone decides to die during so commands in adb. :crying:
Now i cant turn on the phone or boot into fastboot or bootloader. everytime i plug it in the charging light just flashes. Also my computer recognises the device as qualcomm hs-usb qdloader 9008 . ive read around the internet and ive found two methods. blank flash and qfil. issue is those tutorials were made for the moto g5 plus. I have searched around the internet and im beginnign to lose hope now. Can someone tell me how to fix this or give me the right blankflash version.
much appreciated

Im sorry that i cant post a useful reply for your problem that you cant even boot into fastboot / hardbricked phone.
The following link is for all those that are stuck in fastboot mode / boot loop.
This post says its for indian version, but i have EU version (1676) and it worked for me to get back my phone as it was when bought:
https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835

Kim Il said:
Im sorry that i cant post a useful reply for your problem that you cant even boot into fastboot / hardbricked phone.
The following link is for all those that are stuck in fastboot mode / boot loop.
This post says its for indian version, but i have EU version (1676) and it worked for me to get back my phone as it was when bought:
https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
Click to expand...
Click to collapse
Thanks but unfortunately still cant access bootloader or fastboot to do so :/

rajibahmed said:
Thanks but unfortunately still cant access bootloader or fastboot to do so :/
Click to expand...
Click to collapse
if you cant access bootloader take it to a repair shop - you need specialist software and hardware to re-image your phone
how on earth did you do that - you do know to root this device its just a simple zip flashing in recovery mode - no fancy commands or anything required once you have unlocked the bootloader via the very easy to follow guide on the moto unlock bootloader website

TheFixItMan said:
if you cant access bootloader take it to a repair shop - you need specialist software and hardware to re-image your phone
how on earth did you do that - you do know to root this device its just a simple zip flashing in recovery mode - no fancy commands or anything required once you have unlocked the bootloader via the very easy to follow guide on the moto unlock bootloader website
Click to expand...
Click to collapse
Its a long story. Basically i rooted it successfully but one of my favourite apps (snapchat) wasnt letting me sign in because i was rooted. I tried everything to mkae it work. Eventually i tried to unroot sign in and reroot to make it work. At that moment something went terribly wrong idk what but now im hardbricked.

rajibahmed said:
Its a long story. Basically i rooted it successfully but one of my favourite apps (snapchat) wasnt letting me sign in because i was rooted. I tried everything to mkae it work. Eventually i tried to unroot sign in and reroot to make it work. At that moment something went terribly wrong idk what but now im hardbricked.
Click to expand...
Click to collapse
If you are using LineageOS all you had to do was just go into dev settings switch root to disable & restart the phone
If you used magisk just use the magisk uninstaller then reflash the kernel
I don't understand why you touched the bootloader partition

TheFixItMan said:
If you are using LineageOS all you had to do was just go into dev settings switch root to disable & restart the phone
If you used magisk just use the magisk uninstaller then reflash the kernel
I don't understand why you touched the bootloader partition
Click to expand...
Click to collapse
I dunno y either. Luckily I had insurance on it so now I got a new device

Although even though I'm sorted it think we need a way to fix hardbricked devices because the Moto g5plus and g4s have fixes but I haven't found any that work for Cedric devices

rajibahmed said:
Although even though I'm sorted it think we need a way to fix hardbricked devices because the Moto g5plus and g4s have fixes but I haven't found any that work for Cedric devices
Click to expand...
Click to collapse
How did u fix

infixremix said:
How did u fix
Click to expand...
Click to collapse
I had insurance so I just replaced the whole device

rajibahmed said:
I had insurance so I just replaced the whole device
Click to expand...
Click to collapse
Wtf insurance covers it ?

infixremix said:
Wtf insurance covers it ?
Click to expand...
Click to collapse
Ish. I had Argos insurance and they basically take any dead device. Plus they don't check if it's been tampered with . I just said it didn't turn on

rajibahmed said:
Ish. I had Argos insurance and they basically take any dead device. Plus they don't check if it's been tampered with . I just said it didn't turn on
Click to expand...
Click to collapse
Motorola warranty takes hardbricked dvices with locked bootlloadder?

CypherPotato said:
Motorola warranty takes hardbricked dvices with locked bootlloadder?
Click to expand...
Click to collapse
How the hell did u hradbrick ur device without an unlocked bootloader. And idk I think that after you start tampering with the os and system it kills ur warranty. You'll have to chat with someone at Motorola

help phone wont boot into recovery and system after using blankflash

so i was flashing a nougat 7.0 update on moto z play and then all of a sudden my phone wouldnt even power on the screen was all black so i decided to use blank flash. Blank flash did take me to the bootloader but even when trying to boot to recovery and system it wont work.
help plz.

Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
what do you mean

Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.

ahmed12389 said:
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
Click to expand...
Click to collapse
Do you see the device listed in Windows?

Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
yes I can see it

Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
what do you suggest I do

ahmed12389 said:
what do you suggest I do
Click to expand...
Click to collapse
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.

echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
Yes I have flashed stock firmware on my device I remember downgrading to marshmallow then updating back to nougat then my device fully shut down it was all black. After this incident, i did what you would normally do and that was to use blank flash to at least get the bootloader back, as I did get the bootloader I could not use the boot options such as recovery mode. so I am basically stuck on the bootloader and can do nothing. My device is an addison XT1635-02 and before I flashed nougat ota I had the marshmallow December security update.

echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
I also believe my device is hard bricked as I cant access boot options at all it just keeps boot looping once I try to access a boot option. also is it normal for my bootloader to say that my software status is modified because I think after you flash blank flash your software status modified. finally, I have been trying to flash stock firmware but for some reason, gpt and bootloader.img always fail to flash. Thanks for the reply I hope you can help.

echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.

ahmed12389 said:
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
Click to expand...
Click to collapse
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
ok the thing is I am certain I used the wrong blank flash zip therefore meaning that I flashed the wrong things this is probably why I'm boot looping do you have any idea how to revert the changes of blank flash so I can flash the propper blank flash. Is their even any blank flash for Moto z play anyways

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I was flashing the July security patch stock firmware and it's giving me these errors

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
if i flash that stock frimware it takes straight to 7.1.1 is that correct

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one

ahmed12389 said:
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
Click to expand...
Click to collapse
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.

echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight

ahmed12389 said:
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
Click to expand...
Click to collapse
If your device was ever on stock Nougat (7.0 or 7.1.1), then flashing that marshmallow ROM won't likely work in repairing your bootloader. You need a firmware that is the same or newer than the latest firmware your device had. Downgrading stock firmware does not usually downgrade your bootloader, hence the corruption and need to have same or newer firmware to repair. Your bootloader would otherwise reject old firmware via preflash validation errors.
Hopefully the 7.1.1 firmware will help fix things. You will lose data however in the process of flashing your device, so hopefully you have backups.

echo92 said:
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
Click to expand...
Click to collapse
oh my freaking god you fixed it!!! you are literraly my idol thanks to you i dont need to take it to service from now on I'm never flashing again. but thank you very much you fixed my phone you absolute legend.

ahmed12389 said:
what do you mean
Click to expand...
Click to collapse
how is it recognized by the PC in device manager?