hi guys i am looking for a on my rog phone 2 with AVB VERIFY FAIL after 5-6times stuck on logo,
It happen when my phone get battery drain and die, then i recharge it to 90% and tried to power on it stuck on the logo then suddenly AVB VERIFY FAIL show
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In my case, even if I connect Rog Phone 2 via USB, it does not detect it, and even if I press START or Recovery mode on the boot loader, it enters the boot loader, so I can not even recover it on my computer
If press START several times, will get "AVB VERIFY FAIL!!"
What I did was downgrade with the official downgrade file and then update from settings to A10 and I got bootloader loop.
someone help plz.
Reflash phone's Stock ROM.
jwoegerbauer said:
Reflash phone's Stock ROM.
Click to expand...
Click to collapse
Okay.
I try it
jwoegerbauer said:
Reflash phone's Stock ROM.
Click to expand...
Click to collapse
I tried using the attached file but doesn't change.
Still don't detect.
A phone's Stock ROM typically gets flashed via ADB Sideload method and NOT via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload <PATH-TO-STOCK-ROM-ZIP-FILE-HERE>
adb reboot
jwoegerbauer said:
A phone's Stock ROM typically gets flashed via ADB Sideload method and NOT via Fastboot.
Example:
Code:
adb devices
adb reboot sideload
adb sideload <PATH-TO-STOCK-ROM-ZIP-FILE-HERE>
adb reboot
Click to expand...
Click to collapse
impossible
Have you ever successfully enabled "USB Debug" option on phone ( what is required you can access phone via ADB) ?
jwoegerbauer said:
Have you ever successfully enabled "USB Debug" option on phone ( what is required you can access phone via ADB) ?
Click to expand...
Click to collapse
I'm not sure if USB debugging was turned on, but I think it was ON.
I decided send ASUS Service Center
jhie1989 said:
hi guys i am looking for a on my rog phone 2 with AVB VERIFY FAIL after 5-6times stuck on logo,
It happen when my phone get battery drain and die, then i recharge it to 90% and tried to power on it stuck on the logo then suddenly AVB VERIFY FAIL showView attachment 5385729
Click to expand...
Click to collapse
Same
AVB VERIFY FAIL is shown when Stock Android OS got tampered by whatsoever method.
jwoegerbauer said:
AVB VERIFY FAIL is shown when Stock Android OS get tampered by what method whatsoever
Click to expand...
Click to collapse
A10→A9 official downgrade and upgrade to A10 by FOTA.
This is what I did.
Dungle unlock said:
A10→A9 official downgrade and upgrade to A10 by FOTA.
This is what I did
Click to expand...
Click to collapse
did your device get a fix
jhie1989 said:
did your device get a fix
Click to expand...
Click to collapse
nope
jhie1989 said:
hi guys i am looking for a on my rog phone 2 with AVB VERIFY FAIL after 5-6times stuck on logo,
It happen when my phone get battery drain and die, then i recharge it to 90% and tried to power on it stuck on the logo then suddenly AVB VERIFY FAIL showView attachment 5385729
Click to expand...
Click to collapse
Open platform tool type cmd
ADB devices
Reboot to bootloader
Fastboot devices
Fastboot boot twrp.img
Enter and u will get phone back
Related
Bootloop
Hi there, i was on cm7, than i found this rom "Desire XS version 1.1" and I decided to install it, after aroma installation, I rebooted it and now i'm in bootloop and i can't access to hboot, what should I do?
Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.
Thank you for your reply, but i think that i can't access to fastboot
evilken9555 said:
Thank you for your reply, but i think that i can't access to fastboot
Click to expand...
Click to collapse
pull the battery out for a min then put back in, u should be able to boot into bootloader then select fastboot in the menu
Got an update :
Both of the suggestions didn't work, so i've tried to connect my phone to a PC and tried to use adb to access into fastboot mode, once I've got into fastboot I've tried to install the stock firmware through ruu, but I get an error : USB error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#Fear said:
Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.
Click to expand...
Click to collapse
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?
evilken9555 said:
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?
Click to expand...
Click to collapse
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.
jmcclue said:
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.
Click to expand...
Click to collapse
thank you for your support guys, i'll try this in the afternoon =).
I wanted to thank you so much guys, thank you for your help and kindess, i've finally installed the original sense rom =).
Have a good day!
My phone (2nd nexus5, not my daily driver nexus) is stuck in a bootloop (stuck at the booting animation) after updating via the OTA updtes, never rooted or touched any setting in the dev options in the setting menu.
The phone stays like that for hours, doesn't even reboot on its own, just keeps playing the bootanimation for hours and hours until the battery dies.
I have access to the bootloader, and default(stock) recovery.
tried oem unlock, but it doesn't work, and shows no errors.
Tried hard reset from the stock recovery and got numerous E: Failed to mount ..... errors. (check attached photo)
All attempts to wipe or format anypart of the phone fail with the same error,
ADB side load of a custom recovery ( TWRP ) also failed with the same error.
Please help me out, data loss is not an issue as i had no imp data and used it mainly for calls and emails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom
pranavmali said:
Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom
Click to expand...
Click to collapse
It shows an error
FAILED (remote: not supported in locked device)
Like I said, oem unlock doesn't work.
As soon as i give the oem unlock command, it will ask for conformation, after hitting yes,
it will even show LOCK STATE - unlocked.
But as soon as the phone reboots or re-enters bootloader, the phone is back to a locked bootloader.
On unlocking bootloader, flashing TWRP via fastboot, when i enter recovery mode, i am still taken back to the stock recovery.
Try Wug fresh's tool kit! To unlock bootloader
Does the give give an error message when issuing the fastboot oem unlock command?
pranavmali said:
Try Wug fresh's tool kit! To unlock bootloader
Click to expand...
Click to collapse
No effect, still stuck the same way.
below is the live log from the NRT toolkit
Live log initiated [2016-05-19]:
Analyzing factory image; please be patient...
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
Checking ADB/FASTBOOT Connectivity
adb devices
03670030215d290e device
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
fastboot oem unlock
Rebooting your device...
and then suck at bootanimation loop
audit13 said:
Does the give give an error message when issuing the fastboot oem unlock command?
Click to expand...
Click to collapse
when i give the fast boot oem unlock command, it will get executed, my phone will ask for me to manually go to the yes key, hit power button to conform,
I am taken back to the bootloader screen, it shows lock state- unlocked
and the word "erasing..." flashes under it for less than 1 second and thats it...no other change what so ever, as soon as i reboot to bootloader or reboot the phone or do anything, the phone is back to the locked bootloader state.
The emmc is damaged or defective and can only be fixed with a motherboard replacement.
audit13 said:
The emmc is damaged or defective and can only be fixed with a motherboard replacement.
Click to expand...
Click to collapse
is there a sure-shot way of determining that my emmc is damaged ..?
the state that my phone is in now, it would make more sense to just buy a new device rather than replace the motherboard.
or
another option i can consider is the thread - http://forum.xda-developers.com/google-nexus-5/help/nexus-5-64gb-t3350533 for getting a new emmc and replacing, but before i take any actions i would like to know that there is no other option left.
Since you now appear to have nothing to lose, try installing the full N5 OTA image:
https://developers.google.com/android/nexus/ota#hammerhead-for-nexus-5-mobile
The instructions are on the page, or NRT has an OTA option (Advanced utilities/Sideload OTA update).
It may not work if your bootloader is genuinely locked or if the EMMC is really fried, but worst case you can't do any more damage, right?
I just bought my lenovo tab p11 and i decided to do a manual update through lenovo smart rescue assistant because my device has an old firmware and can't OTA update. The thing is, i forgot to do OEM unlock on my device although i did do USB debugging. I have successfully install the updated firmware on my device but i am stuck on fastboot mode which i can't select anything even if i select any of the option it keeps on booting to fastboot mode. The only option working is the Power off option. How do i fix this? Please help
You can try to reset tablet to Normal mode ( means boot into Android OS ) running
Code:
adb devices
adb reboot
jwoegerbauer said:
You can try to reset tablet to Normal mode ( means boot into Android OS ) running
Code:
adb devices
adb reboot
Click to expand...
Click to collapse
Hi! Thanks for replying, i'm new to this kind of thing but do i need to EDL mode my device before doing this? also i tried the adb thing but i the list for devices is empty although my device is connected to my pc.
Make sure your device is NOT connected as a media device ( means in MTP mode ).
Turn on USB debugging
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Use USB cable that came with tablet.
jwoegerbauer said:
Make sure your device is NOT connected as a media device ( means in MTP mode ).
Turn on USB debugging
Use USB cable that came with tablet.
Click to expand...
Click to collapse
I can't do this method because i can't get out to fastboot mode :'(
Then try this
Code:
fastboot devices
fastboot reboot fastboot
fastboot reboot
jwoegerbauer said:
Then try this
Code:
fastboot devices
fastboot reboot fastboot
fastboot reboot
Click to expand...
Click to collapse
Hi again. Sorry for the long inactivity. I tried this method and it shows me:
" fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
PS C:\Users\jaeru\Desktop\lenovo flash pls work\platform-tools> "
what should i do next? I'm really sorry for asking too much :'(
Pupa231 said:
Hi again. Sorry for the long inactivity. I tried this method and it shows me:
" fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
PS C:\Users\jaeru\Desktop\lenovo flash pls work\platform-tools> "
what should i do next? I'm really sorry for asking too much :'(
Click to expand...
Click to collapse
Don't connect your device to PC. Press same time volume up+ volume down + power for seconds and your device will reboot.
Use a linux distribution, install fastboot and try:
fastboot set_active a
Amatöhr said:
Use a linux distribution, install fastboot and try:
fastboot set_active a
Click to expand...
Click to collapse
failed : not unlocked
~$ fastboot flashing unlock
should help you to fix this.
VOL"UP"+POWER doesn't work
[email protected] said:
VOL"UP"+POWER doesn't work
Click to expand...
Click to collapse
Adb reboot fastboot
linccracker said:
Adb reboot fastboot
Click to expand...
Click to collapse
When smart in boot loop))
[email protected] said:
When smart in boot loop))
Click to expand...
Click to collapse
Will it not boot into recovery mode? Vol -down and power button
linccracker said:
Will it not boot into recovery mode? Vol -down and power button
Click to expand...
Click to collapse
I tried to uninstall system apps. after an unsuccessful experiment, the phone went into the bootloop. Stock recovery was a possible only with data reset. I wanted to restore system with fastboot but it was not available. Just a hard reset. but is no longer relevant. went to the hardreset. ))
How to unlock bootloader in Oppo a54 cph2339
John. P. John said:
How to unlock bootloader in Oppo a54 cph2339
Click to expand...
Click to collapse
Use mtk client
linccracker said:
Adb reboot fastboot
Click to expand...
Click to collapse
Its shows don't match key or reboot system automatically... Please help me
Deepjatt7 said:
Its shows don't match key or reboot system automatically... Please help me
Click to expand...
Click to collapse
Sorry don't have this phone anymore to try
Deepjatt7 said:
Its shows don't match key or reboot system automatically... Please help me
Click to expand...
Click to collapse
Oppo phones have it's bootloader locked, there used to be method to break it but they fixed it in 2020 security update. So ig there is no way to unlock it.
adb reboot fastboot, in the exact same time that the command ends its process, disconnect USB from device, just 2 seconds, and reconnect again, it will show a fastbootd screen with the exact same menu that recovery.
Pressing and tapping on the recovery version also leads to download mode, specially useful for Qualcomm models.
This works for many Realme devices. Anyway, in a locked device, there’s no much to do through.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fal3n.4ngel said:
Oppo phones have it's bootloader locked, there used to be method to break it but they fixed it in 2020 security update. So ig there is no way to unloc
SubwayChamp said:
adb reboot fastboot, in the exact same time that the command ends its process, disconnect USB from device, just 2 seconds, and reconnect again, it will show a fastbootd screen with the exact same menu that recovery.
Pressing and tapping on the recovery version also leads to download mode, specially useful for Qualcomm models.
This works for many Realme devices. Anyway, in a locked device, there’s no much to do through.
View attachment 5574189
Click to expand...
Click to collapse
I'm stuck at this same point
Click to expand...
Click to collapse
@armwaypaul What exactly did you want to write?
so, i was trying to install twrp, but i made a stupid mistake, instead of fastboot flash recovery i did fastboot flash boot, now it tells me: "the current image(boot/recovery) have been destroyed", when i go into bootloader, and attack the cable (both before and after) restarts itself.
things I tried: flash the original boot (it gave "FAILED (Write to device failed (no link))", obviously before the bootloader happened) change usb cable, flash the stock rom (obviously before the bootloader happened)), redownload adb /fastboot drivers, phone drivers, and google drivers. this is all i remember trying to do, i'm desperate, could someone help me please?
update: now i can use bootloader
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
try going into the bootloader and re-unlocking it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Angel1104 said:
View attachment 5798249That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Click to expand...
Click to collapse
I don't understand if the recovery works or not, it's a bootloop with locked bootloader and you can go into recovery or locked bootloader without accessing recovery? you are confusing me, however, if you have access to recovery download the stock rom from the recovery, if not, try to unlock the bootloader again by doing fastboot flashing unlock, then flash the stock recovery and then download the stock rom from the recovery
And how do you enter that mode without the application?
enter bootloader and do fastboot reboot recovery, in bootloader you can't perform flashing actions and many other things (bootloader locked) but some things, like reboot should work
in case you get the same error for the recovery you have to unlock the bootloader again
Can I send you a private message?
yes
Did you solve it? I'm facing the same issue.
Gamer_Mida said:
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Click to expand...
Click to collapse
I am having trouble understanding what you did exactly. I am getting this same error with a Xiaomi Mi 8 Lite.
Edit: got it working by disconnecting all usb ports and trying another port.
Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
same as me i dont know what to do