Database Info

[Q] NEXUS 5 BRICKED TRYING TO ROOT WITH CF AutoRoot. HELP!?

Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.

Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?

abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot

Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.

abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?

Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?

abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?

Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.

abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.

abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.

pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.

pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.

Would opening the command prompt window with administrative rights make a difference? Worth a shot.

Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.

Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.

It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.

[Q] RMA

I just bought a Nexus 5 recently but it's flash memory go corrupt so I request a RMA and got a new one already. However, as the flash memory is corrupted, I can not restore the device to it's original state. I have not flashed a custom rom, but I have unlocked the boot loader, flash custom recovery, root it and flash a new boot animation. What would be the worst thing to happen?

nerodarknight said:
I just bought a Nexus 5 recently but it's flash memory go corrupt so I request a RMA and got a new one already. However, as the flash memory is corrupted, I can not restore the device to it's original state. I have not flashed a custom rom, but I have unlocked the boot loader, flash custom recovery, root it and flash a new boot animation. What would be the worst thing to happen?
Click to expand...
Click to collapse
Unless they can prove that you broke the flash memory by unlocking the bootloader, it'll be fine

rootSU said:
Unless they can prove that you broke the flash memory by unlocking the bootloader, it'll be fine
Click to expand...
Click to collapse
Thank u, it has been troubling me ever since

So, you bought a new nexus 5 before sending the other to RMA and, you want to "clean" the old before sending it ?
Well, can you boot it in fastboot ? If so, try flashtool and flash factory images ?

Charlus97 said:
So, you bought a new nexus 5 before sending the other to RMA and, you want to "clean" the old before sending it ?
Well, can you boot it in fastboot ? If so, try flashtool and flash factory images ?
Click to expand...
Click to collapse
No they sent me a new one alreadt, and now I have to return the broken one to them. About your suggestion, I did try but because the flash memory is corrupted, u can't write or read anything from it, including the OS

Wow. Google sent you a new phone before you've sent them your old ? Never seen that before
But like rootSU said, unless they're able to prove that it's your fault, there's no problem.
But, if you're able to boot into recovery/fastboot, you should be able to restore the orignal recovery & relock the bootloader, no ?

Charlus97 said:
Wow. Google sent you a new phone before you've sent them your old ? Never seen that before
But like rootSU said, unless they're able to prove that it's your fault, there's no problem.
But, if you're able to boot into recovery/fastboot, you should be able to restore the orignal recovery & relock the bootloader, no ?
Click to expand...
Click to collapse
This is how Google does RMA's they send you a new device and put a hold on your credit card equivalent to the price of the device. The hold is removed upon them receiving your old device.

Oh, ok. I used to see RMA like Asus : We pick your device, you wait 3 weeks and, if you're lucky, we will sent it back to you for free.

Just had a doubt about the RMA?
I purchased the device from India and the RMA process is like they pick up the device inspect it and send the replacement.
They collected mine yesterday.
They did mention that the device will be inspected by a technical team,now when i requested them for a replacement over telephone they asked me to send them pictures of the phone and then after reviewing them they notified me that they could now initiate a replacement,so what do they inspect for exactly?
and will they be sending me a new device?

well, I relock it but as soon as I turn it off, it got unlock again, I don't know why

Sonone said:
Just had a doubt about the RMA?
I purchased the device from India and the RMA process is like they pick up the device inspect it and send the replacement.
They collected mine yesterday.
They did mention that the device will be inspected by a technical team,now when i requested them for a replacement over telephone they asked me to send them pictures of the phone and then after reviewing them they notified me that they could now initiate a replacement,so what do they inspect for exactly?
and will they be sending me a new device?
Click to expand...
Click to collapse
They're checking for anything that could would void the warranty, such as user damage or a colourized water damage indicator.
LG RMA works differently from Google RMA. It's the traditional wait a few weeks until your phone is fixed, versus cross shipping of the device so you're never without a phone.

[Q] Accidentally bricked Nexus...I think...

Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...

D0UBLEJUMP said:
Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...
Click to expand...
Click to collapse
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions: https://developers.google.com/android/nexus/images

krs360 said:
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions
Click to expand...
Click to collapse
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.

D0UBLEJUMP said:
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.
Click to expand...
Click to collapse
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.

theesotericone said:
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.
Click to expand...
Click to collapse
Bootloader always relocks when the phone restarts :/

It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.

BirchBarlow said:
It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.
Click to expand...
Click to collapse
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?

D0UBLEJUMP said:
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?
Click to expand...
Click to collapse
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag

nexus.freak said:
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag
Click to expand...
Click to collapse
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?

Niflheimer said:
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?
Click to expand...
Click to collapse
Woohoo! Flag reset!
Judging by what I found when I was looking around it doesn't seem like bad emmc is too common, couldn't find many suffering the same issues as me.
As for triggers, my brother's Nexus worked completely fine just like mine, then powered off, powered on, and broken. So...I guess the message of the story is to never turn them off (or try reflash) and they'll be fine?

If you bought phone of play store you can send it to google, there was a tread here some time ago and it said that google accept to replace phones with temper flag and unlocked bootloader.
Good luck

HELP!!!!!! Locked bootloader after flashing a kernel and it doesn't want to boot

Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!

Colday96 said:
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Click to expand...
Click to collapse
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.

phaino00 said:
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
Click to expand...
Click to collapse
I bought the phone on ebay. Could i still get a RMA replacement ?

Colday96 said:
I bought the phone on ebay. Could i still get a RMA replacement ?
Click to expand...
Click to collapse
I don't believe so since you're not the original owner. However, it doesn't hurt to try.

If you bl locked the phone w modified software ur boned. I believe that RMA availability is transferrable from owner to owner, however, I also believe that they will refuse to RMA a phone which technically broke because AVB is doing its job properly. You can try but I'd say your chances are slim. Sorry mate. Also future reference: if you don't have any reason in particular to relock your phone, just don't. You'll save yourself the hassle of having to do it again and it wiping the phone everytime any software thing goes wrong or anytime u want to upgrade custom ROM or kernel or anything of the sort. This goes for any phone not just those with android verified boot.

phaino00 said:
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
Click to expand...
Click to collapse
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?

Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Assume they will.

Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Yes they will know but they have proprietary software to forcefully unlock/reformat the phone properly if they so choose to actually accept the phone

This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?

Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Click to expand...
Click to collapse
You can still sell it for around 150 for parts on ebay

Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400
Click to expand...
Click to collapse
Can't you restore using the stock zips from google?

Poebat said:
Can't you restore using the stock zips from google?
Click to expand...
Click to collapse
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail

Nandolkz said:
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Click to expand...
Click to collapse
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?

Poebat said:
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Click to expand...
Click to collapse
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...

Nandolkz said:
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Click to expand...
Click to collapse
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat

Poebat said:
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Click to expand...
Click to collapse
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?

Colday96 said:
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Click to expand...
Click to collapse
He doesn't have a working OS so I doubt it

Here is what is happening to me... Any ideason how to fix it? ?

Nandolkz said:
Here is what is happening to me... Any ideason how to fix it? ?
Click to expand...
Click to collapse
Try flashing the stock rom with fastboot

Poebat said:
Try flashing the stock rom with fastboot
Click to expand...
Click to collapse
Here

Question EDL mode (9008 mode) Please Help To Fix

Hi guys
Please help me to solve my problem. I tried several methods but unfortunately it was not solved. Does anyone have a suitable solution?
My Phone Rog phone 5 ww ver bootloader Locked

Jamshid66 said:
Hi guys
Please help me to solve my problem. I tried several methods but unfortunately it was not solved. Does anyone have a suitable solution?
My Phone Rog phone 5 ww ver bootloader Locked
Click to expand...
Click to collapse
What is the specific problem you are trying to fix?

twistedumbrella said:
What is the specific problem you are trying to fix?
Click to expand...
Click to collapse
My phone (Rog phone 5) turned off and didn’t turn on!!
After connecting to PC, it enters to EDL Mode and doesn’t exit from it!!
Help me that how can exit it from EDL Mode and use my phone again!?

Jamshid66 said:
My phone (Rog phone 5) turned off and didn’t turn on!!
After connecting to PC, it enters to EDL Mode and doesn’t exit from it!!
Help me that how can exit it from EDL Mode and use my phone again!?
Click to expand...
Click to collapse
What were you doing when it started? Did you unlock the bootloader? Was it rooted? Did you flash something?

twistedumbrella said:
What were you doing when it started? Did you unlock the bootloader? Was it rooted? Did you flash something?
Click to expand...
Click to collapse
It went to this state when the mobile phone was finished charging

Jamshid66 said:
It went to this state when the mobile phone was finished charging
Click to expand...
Click to collapse
It's a completely stock phone? You've never unlocked the bootloader or tried to flash anything?
If that's the case, you'd be far better off contacting Asus about it. It is well within the year warranty and you may require a special cable to flash it correctly yourself. It sounds like it may be defective, so even recovering it could only be temporary.
Contact Us | ASUS

twistedumbrella said:
It's a completely stock phone? You've never unlocked the bootloader or tried to flash anything?
If that's the case, you'd be far better off contacting Asus about it. It is well within the year warranty and you may require a special cable to flash it correctly yourself. It sounds like it may be defective, so even recovering it could only be temporary.
Contact Us | ASUS
Click to expand...
Click to collapse
I talked to the support department but did not answer
Is there a way I can do it?
I feel my bootloader is broken

Jamshid66 said:
I talked to the support department but did not answer
Is there a way I can do it?
I feel my bootloader is broken
Click to expand...
Click to collapse
Probably need a deep flash cable, I believe it's called

twistedumbrella said:
Probably need a deep flash cable, I believe it's called
Click to expand...
Click to collapse

It says they are updating the page. You probably won't hear back over the weekend and they take a couple days to reply normally. It is the safest way to restore the phone, though.
Making cables and using software that doesn't come directly from Asus for restoring from a brick is risky. It's a last resort when they say they won't help.

twistedumbrella said:
It says they are updating the page. You probably won't hear back over the weekend and they take a couple days to reply normally. It is the safest way to restore the phone, though.
Making cables and using software that doesn't come directly from Asus for restoring from a brick is risky. It's a last resort when they say they won't help.
Click to expand...
Click to collapse
If I want to do it myself, what do you suggest because I got the phone from another country, I do not think the warranty is included

Jamshid66 said:
If I want to do it myself, what do you suggest because I got the phone from another country, I do not think the warranty is included
Click to expand...
Click to collapse
I suggest looking at how they did it on the ROG Phone 3 and then seeing what, if any, of that has a matching ROG Phone 5 version. This phone is only a couple months old, so there isn't a whole lot of public research yet.

twistedumbrella said:
I suggest looking at how they did it on the ROG Phone 3 and then seeing what, if any, of that has a matching ROG Phone 5 version. This phone is only a couple months old, so there isn't a whole lot of public research yet.
Click to expand...
Click to collapse
Do you mean that I have to use files that referse to Rog phone 3 ?

Jamshid66 said:
Do you mean that I have to use files that referse to Rog phone 3 ?
Click to expand...
Click to collapse
No. That will break the phone much worse.

twistedumbrella said:
No. That will break the phone much worse.
Click to expand...
Click to collapse
So we have to wait for more files For ROG 5

Jamshid66 said:
So we have to wait for more files For ROG 5
Click to expand...
Click to collapse
I honestly don't know. Hopefully someone else will come along that can help.

twistedumbrella said:
I honestly don't know. Hopefully someone else will come along that can help.
Click to expand...
Click to collapse
what is your suggestion?

Jamshid66 said:
what is your suggestion?
Click to expand...
Click to collapse
Wait to hear back from Asus

twistedumbrella said:
Wait to hear back from Asus
Click to expand...
Click to collapse
I speak with a warranty, unfortunately my request was rejected

Jamshid66 said:
I speak with a warranty, unfortunately my request was rejected
Click to expand...
Click to collapse
If the device is under warranty and this happened without you altering anything I don't understand how they can reject it
If the device is only stuck in EDL mode but no hardware damage and has a working bootloader you can try (entirely at own risk):
1 - Make (or buy) a deep flash cable and see if you can snap it out of EDL mode by activating it a few times while the device is connected. (Chances are slim but it does work sometimes).
2 - Disconnect and re-connect the battery pack from the mainboard. The battery connector of ROG 5 is located on the right side between the north battery and the mainboard when looked from the back. You need to remove the top part of the motherboard for access to it. It's not a huge operation but requires some basic tools and some phone adhesive for closing the backcase again. Some cooling paste is also useful to repaste the heat conducting parts before closing it again (optional).
However, if the device doesn't have a working boot and/or it's really damaged then all above is useless.