Database Develop

[Q] HARD Bricked Nexus 6 PLEASE HELP!!

My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.

can you get a custom recovery on successfully.........?
did you flash the stock image manually?

mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.

jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!

by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....

Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.

I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:

my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........

ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.

jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.

Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...

jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?

[notice] please read!!!

They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.

I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?

U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk

Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.

rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
I've heard it called a "sponge" I like that lol

shard111 said:
I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?
Click to expand...
Click to collapse
coldconfession13 said:
U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
i flashed each file separately yes no errors when flashing everything went through okay but still wont pass google screen

If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk

coldconfession13 said:
If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
no.
but after flashing the factory img, you might have to wipe data for it to boot.

jeromechrome1 said:
They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
Click to expand...
Click to collapse
NONE of this suggests that your phone is a brick. In fact, it all proves that it is NOT a brick.
*which is not to say that it isn't BROKEN.
"i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C"
Let me ask you this; did it reboot when you booted into a custom recovery? If custom recovery worked, then it seems like the unit can still be saved.
BTW: LRX22C is also 5.0. Specifically, 5.0.1. 5.1 is not available yet.
So a little bit of clarifications first;
HAVE you tried to perform a factory wipe (via recovery) or otherwise FORMAT (not "fastboot erase") the data and cache partitions? No part of your message mentions formatting the data or cache partitions. If the init is unable to manipulate/mount a possibly corrupt data or cache partition (or possibly some other partitions as well), then it WILL REBOOT.
In addition, some logs of the reboot could be useful if you are able to obtain any. A somewhat modified boot image can enable adb and kernel logging at a point from before the reboot occurs.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I don't think you need a new mainboard.
If what he explained to you is correct, then my previous about fixing corrupt data partitions should solve the issue for you.

Agree with the guy above me. Same thing happened to me on my Nexus 9. Manual flashes all successful but could not boot. Booted into recovery and did a factory wipe and all was well. I know this is the nexus 6, but it sounds like corrupted data.

Mi3 bootloops, refuses to enter twrp recovery mode

Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!

try to flash official twrp recovery via fastboot

Rahuljs said:
try to flash official twrp recovery via fastboot
Click to expand...
Click to collapse
How to flash it ?? Method pls...
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!

Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?

Try flashing the phone via MIUI flashing tool as you were able to access fastboot mode
http://en.miui.com/a-234.html

xypherize said:
Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!
Click to expand...
Click to collapse
Here is the link for tutorial for flashing recovery via fastboot mode. All commands are same just download the twrp recovery image from here. DON'T FORGET TO RENAME THE IMAGE FILE, BECAUSE ADB DOESN'T RECOGNISE ANY SPECIAL CHARACTER.

what did you do ? I'm stuck in the same situation word by word.
did you solve this issue ?

yohaneseko said:
Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?
Click to expand...
Click to collapse
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.

Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
rxl.noir said:
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.
Click to expand...
Click to collapse

yohaneseko said:
Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
Click to expand...
Click to collapse
Heyaa~
For the battery, you could easily found it on Tokopedia started from 110k, although most of them are shipped from Jakarta. The replacement process is quite easy, you might only need #0 Phillips or any small plus screwdriver, a plastic card (for spudge replacement), and some guts :q. The details and steps are on my prev. post.
I haven't tried to sent it to the seller/distributor, since it might take a long time to get it done.

Just a little update;
I replaced my battery on my Mi3 that have the same exact case as yours, and it finally works. No more short bootloop, no more stuck in fastboot.

Bootloop

I just wanna ask after the oct update i got bootloop now when i try to go to service center they told me that the problem is the motherboard. When i explain to them the reason i just update it then bootloop they always tell me the problem is motherboard. And i need to fix it and the cost is half the price of the phone. Now i need some help. When i try to turn on its stuck to androide one then off whne i try to go to fastboot its okay. When i charge it it turns on and off. I jus need some help.

mrvonzuela said:
I just wanna ask after the oct update i got bootloop now when i try to go to service center they told me that the problem is the motherboard. When i explain to them the reason i just update it then bootloop they always tell me the problem is motherboard. And i need to fix it and the cost is half the price of the phone. Now i need some help. When i try to turn on its stuck to androide one then off whne i try to go to fastboot its okay. When i charge it it turns on and off. I jus need some help.
Click to expand...
Click to collapse
is your bootloader unlocked?
If so, have you tried booting latest twrp image from fastboot?
Code:
fastboot boot twrp.img
Sounds like you may at least have to try to wipe and format your phone at the cost of all data.
But then you could use the situation to install a good custom ROM..

If you were doing a normal update, your phone should revert to the previous slot after a few attempted reboots.
Keep trying to reboot.
If nothing else works, try flashing september version from EDL (search it on the forums).
I flashed and still couldn't boot at first. I tried restarting a lot of times, until it got on the "Retry" or "Power off" option. I let the phone sit on this screen until it shut itself off. After tried booting up a few more times until it finally did.
I was not plugged in during this.
I'm not going near that october patch ever again.

Hello everyone,
I'm using mi A2 (64gb). It is rooted and was running on Resurrection Remix 8.6.2. Somedays earlier, I let my phone idle, suddenly it starts rebooting, just like bootlooping. After seeing that I booted in recovery and wiped dalvik and cache then rebooted and the phone rebooted in system successfully. But then I noticed the power menu appearing continuously on the home screen, I tried to dismiss it but it rebooted again and so on. From then, only the splash screen appeared for 8 seconds and it reboots again. I can boot into recovery or fastboot but only for 2-3 seconds then it reboots.
I've searched on the internet and was flashing firmware manually from fastboot but accidentally, I flashed an image file in a wrong location and the phone screen turned off and nothing appeared. Then I found that it had entered in EDL mode. but still it is rebooting and I can't flash firmware from mi flashing tool as fastboot wasn't working.
This is the problem of my phone. A help would be amazing! Thank you!
Ps. I'm new here and it is my first post so if anything is wrong. I beg your pardon and sorry for my bad English.

Rm789 said:
Hello everyone,
I'm using mi A2 (64gb). It is rooted and was running on Resurrection Remix 8.6.2. Somedays earlier, I let my phone idle, suddenly it starts rebooting, just like bootlooping. After seeing that I booted in recovery and wiped dalvik and cache then rebooted and the phone rebooted in system successfully. But then I noticed the power menu appearing continuously on the home screen, I tried to dismiss it but it rebooted again and so on. From then, only the splash screen appeared for 8 seconds and it reboots again. I can boot into recovery or fastboot but only for 2-3 seconds then it reboots.
I've searched on the internet and was flashing firmware manually from fastboot but accidentally, I flashed an image file in a wrong location and the phone screen turned off and nothing appeared. Then I found that it had entered in EDL mode. but still it is rebooting and I can't flash firmware from mi flashing tool as fastboot wasn't working.
This is the problem of my phone. A help would be amazing! Thank you!
Ps. I'm new here and it is my first post so if anything is wrong. I beg your pardon and sorry for my bad English.
Click to expand...
Click to collapse
Try shorting testpoint in motherboard then enter EDL mode,
Then use mi flash tool.need to remove battery first.
How? Watch youtube, for mi6x. Mi 6x = a2, sort of.
~yes, you need to remove/open the phone.

shizuni said:
Try shorting testpoint in motherboard then enter EDL mode,
Then use mi flash tool.need to remove battery first.
How? Watch youtube, for mi6x. Mi 6x = a2, sort of.
~yes, you need to remove/open the phone.
Click to expand...
Click to collapse
Thank you for replying
One thing to note I'm in edl mode already. Do I need to short the test points again?

Rm789 said:
Thank you for replying
One thing to note I'm in edl mode already. Do I need to short the test points again?
Click to expand...
Click to collapse
U said rebooting even in edl, if not. Dont. Just make sure you have enough battery juice.
Use xiaomi tools. Or not, I uncompressed the file and click flash all.

shizuni said:
U said rebooting even in edl, if not. Dont. Just make sure you have enough battery juice.
Use xiaomi tools. Or not, I uncompressed the file and click flash all.
Click to expand...
Click to collapse
Yes, phone is rebooting in edl mode. I also charged it to around 40 minutes before connect it to pc but no hope. I got it
Thank you so much for the clarification.

i have a similar issue, phone reboots when flashing reached vendor b and goes into bootloop, anybody ?

Rog phone 2 stuck on a bootloop without ever trying to install a custom rom

I have my rog 2 stuck in a bootloop. I don't really know why in the first place, because I don't like to change and mess around with custom roms. So i've never done that.
The case was that I was watching a video on YouTube and suddenly the touch screen stopped responding, the phone kept responding to other inputs such as the power button and the volume rocker. So I decided to restart the phone. And then it didn't turn on again. Got stuck in a boot loop.
I've been trying to fix it for a long time. But I just can't do it. Nor am I able to see what is happening with the phone. I have used this guide.
EVERYTHING works perfectly, it doesn't give me any errors during flashing or anything like that. Even the program tells me that the rom has been flashed correctly, and even the rog logo during boot, changes (I suppose because it is a version of the rom prior to the one I had.). The fact is that even with that the phone is still stuck in the bootloop. I have tried more things but this is the one that has taken me the furthest. I don't know what else to try. If anyone has any ideas, please tell me.
P.D. Sorry if my English is a bit rusty.

go back to stock and try other rom.

atoyu said:
go back to stock and try other rom.
Click to expand...
Click to collapse
Any suggestions which rom I can use? I have tried the rom of the guide and the ones that Asus has on their website. None of them have bailed me out.

@Arnau17 Any Updates? I am facing the same issue. Mine reaches till boot logo and then freezes and reboots again. Tried flashing stock ROM as well but no Luck

I am in the same situation, tried several raw rom files, still in bootloop

USB plug correctly on side USB port? can you enter recovery or fastboot mode?
i have same problems before, if fixed after flash RAW rom, hope this help.

is there a guide to fix AVB VERIFY FAIL on Rog Phone 2