1801P - Unrecoverable bootloader error (0x00000008) - Android Q&A, Help & Troubleshooting

Hello, everyone.
I'm not sure if this is the right forum.
My 1801P was trapped in a bootloop.
Then I tried to reset it with Power+VOL- -> Wipe.
Well, the stupid thing is now apparently the bootloader is gone.
Signature mismatch
Booting failed
Unrecoverable bootloader error (0x00000008).
Can someone help me?

Same Problem
Hello everybody,
I have two stock ASUS P1801 and one got stuck in this bootloader error. It happened once or twice and I was able to restart it until the last reboot.
I have still access to the recovery and I did a "wipe data" that did not solve the problem. Unfortunately, this was also the only solution proposed by the ASUS customer service.
I downloaded the original firmware on a SD card but I think it was not loaded on the P1801 because I don't know the naming convention for the zip file.
Do you think it is also possible to use fastboot to flash it even if the bootloader is not unlocked?
Thanks for your advices.

Related

[help] bricked my moto z

Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks

Asus MemoPad 10, invalid boot

Hey guys! I'm writing, because I screwed up so much and need your help. Well, let's begin:
I wanted to install CM13 on my tablet. It was rooted, but I forgot that bootloader is locked.. Flashed TWRP through the app, rebooted and.. I've got big red warning: Can't load Invalid boot image !!!
This is how it is. The biggest problem is, I can't somehow flash anything, software, boot.img, new recovery, because everytime I got info in console: Cannot flash before unlock.
I've read that you need to download official Asus app to unlock bootloader, but I can't get an access to it right now, because I can't boot my Asus Any ideas what am I supposed to do?
Thanks in advance, cheers!

twrp getting stuck at "updating partition details"

Hi, so I am having a problem with trying to root my motorola XT1775 but more specifically is with the flashing via twrp. So I believe I install the right twrp image and unlocking the bootloader properly for my phone (qualcomm processor), however, whenever I try to flash/make backup via twrp, the process will hang at "updating partition details." So I cannot really flash anything that involves "updating partition details" (probably everything would require this step?). In fact, I am stuck at "updating partition details" for the whole day now when trying to flash magisk. I may have bricked my phone, I don't know. Please help me understand what may be causing this problem and is there a way to fix it? thank you so much for any pointer!
this is the twrp image that I got for my phone:
https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154

Think I have bricked my phone

I recently installed a rom using the fastboot method and inadvertantly locked my phone during the install. The rom installed fine but now in a boot loop with this message " Find Device Storage Corrupted. Your Device Is Unsafe Now". I have also lost my twrp recovery so seem to be locked out of any form of recovery. Any ideas before i bin the phone in frustration.
pipin18 said:
I recently installed a rom using the fastboot method and inadvertantly locked my phone during the install. The rom installed fine but now in a boot loop with this message " Find Device Storage Corrupted. Your Device Is Unsafe Now". I have also lost my twrp recovery so seem to be locked out of any form of recovery. Any ideas before i bin the phone in frustration.
Click to expand...
Click to collapse
I remember that way to flash rom has options to lock your phone back. 1st you have to unlock your phone then flash rom back ( remember to untick lock the phone after flash ) try it. Hope my advices can help you.
Unfortunately I cannot get into my phone to sign into my miui account or turn on debugging. I am in a boot loop so cannot do anything.
My problem still persists and would appreciate any help please....
pipin18 said:
I recently installed a rom using the fastboot method and inadvertantly locked my phone during the install. The rom installed fine but now in a boot loop with this message " Find Device Storage Corrupted. Your Device Is Unsafe Now". I have also lost my twrp recovery so seem to be locked out of any form of recovery. Any ideas before i bin the phone in frustration.
Click to expand...
Click to collapse
I have faced this problem just like you. Here is how you unbricked your phone.
Search for " test point method for redmi 5 plus" and follow their guide. Good luck!
Tried the test point method and worked perfectly................thanks Sai000..........back to normal

Question Nord 2, can't re-lock the bootloader, help!

I've been trying to do so for a week, but just can't do it.
I've tried two way:
I've locked the bootloader from fastboot-mode, shutdown and then got into BROM-mode to re-flash the "boot", "recovery" and "vbmeta" (tried "dtbo" too) images. Then I enter the recovery, I format the data and after that it gives me the "normal" corrupted recovery error.
I've also tried to flash the partitions and lock the bootloader through the same fastboot "session" but I just can't get it done.
I'm on OOS11 A19 (european), I haven't ever upgraded to anything over C.01 (I read that C.05 and beyond would break the BROM-mode). A guy on YouTube did it with A13/15 (indian) but I don't know if it's because of this. This is the first phone I ever mod and sure this is a nightmare (I'm coming from an unofficial PixelExperience).
pasqchia84 said:
I've been trying to do so for a week, but just can't do it.
I've tried two way:
I've locked the bootloader from fastboot-mode, shutdown and then got into BROM-mode to re-flash the "boot", "recovery" and "vbmeta" (tried "dtbo" too) images. Then I enter the recovery, I format the data and after that it gives me the "normal" corrupted recovery error.
I've also tried to flash the partitions and lock the bootloader through the same fastboot "session" but I just can't get it done.
I'm on OOS11 A19 (european), I haven't ever upgraded to anything over C.01 (I read that C.05 and beyond would break the BROM-mode). A guy on YouTube did it with A13/15 (indian) but I don't know if it's because of this. This is the first phone I ever mod and sure this is a nightmare (I'm coming from an unofficial PixelExperience).
Click to expand...
Click to collapse
Okay brother, seems like you have flashed wrong boot img. Flash this boot img. Hopefully your issue will be fixed.

Categories

Resources