Hi there! I have this question which I'd love to have answered because I've been on this issue for around 2 days straight.
Long story short:
Tried to flash custom recovery using fastboot, didn't work because bootloader locked
Kept on trying the unlocker apps, none of them even installed fully (THIS WAS WHEN I WAS STILL ON LOLLIPOP)
Somehow, at some point, I just randomly rebooted and BOOM THERE WAS TWRP (Sorry, I don't remember how exactly I managed that. As far as I remember, I was only using fastboot and nothing else)
Flashed CM 14.1 unofficial, device gave an error message regarding boot.img (something like "could not load boot.img"
Used stock ROM to flash OTA Android 6.1
Now the Asus unlocker app downloads but on reboot it says "error: unlock fail !!!"
Obviously, fastboot is unable to flash a recovery right now. I tried ignoring the error message and rebooting to recovery to stop the device from loading the stock recovery again but the device still loads the stock recovery.
I'm really tired
P.S: NO, there is no Enable OEM option in my Developer Options menu and YES, I have all the drivers necessary.
Did you get anywhere with this? I have a similar problem except that I couldn't flash Android 6.1 because the vendor had flashed WW 5.0.2 on a CN phone without also updating the CN recovery to WW. So the update failed its consistency check.
I've got TWRP on there now, but can't unlock the bootloader in 5.0.2 - I think this is why TWRP can't flash anything. It can't see the update files, won't switch to external SD, etc. .
I also found and tried flashing a WW recovery but that didn't work either. I'm wondering now if I got the 615 software by mistake.
Hey i tryed it to flash a custom pre rooted rom in fastboot i did it well and i wipe factory but when i started for the first time it when in to bootlook...starts when you have to put the language and restarts alone ober and over again...
So i try to flash the stock rom i downloaded from official asus site when i try to flash via adb sideload says cant read zip if i flash by sd card its stay stuck verify uptade package...
Should i get unlock bootloader so that way the rom that is on the phone to work...
What can i do help please
Trying to flash a rom on my HTC 820 (d820n), Stuck at "Main Version is older".
So one dark day, i woke up to my phone being stuck on a Bootloader loop, So after a lot of attempts to get it out of this state, i decided to unlock the bootloader, install custom recovery, wipe /system and install a new ROM, The image i'm trying to install is a stock Marshmallow image (after relocking the bootloader of course) but for some reason i get a message on the bootloader saying "Main Version Is Older Update failed."
Any ideas how i may get my phone alive again?
I have updated my phone with 331 october update, and somehow removed TWRP , bootloader is unlocked ... now I am unable to flash to TWRP or fastboot to stock 2407. getting errors in fastboot mode. checked with different OS , no luck. Cant even downgrade via the stock recovery... please help guys
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Kj1594 said:
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Click to expand...
Click to collapse
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Himanshu.Shukla said:
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Click to expand...
Click to collapse
I did try to install codeworkx twrp recovery, for the Oreo build but it was giving me a hard brick, ie. A black screen and a blue LED when trying to boot to recovery. But as I said, using Unbrick tool v4.0.8 I was able to restore to Oxygen Os 5.1.7 and then everything worked fine.
I am just unsure why it didn't work with Oxygen Os 4.5.8
I mean, with a locked bootloader and a freshly installed OS, you should be able to get OTA updates, right? But the system update was failing. So maybe there was something wrong with the partitions? I don't know. The bootloader in the older Unbrick tool was different than stock. Maybe that was a fault, well, I'll never know. But all I'm saying is, newer Unbrick Tool worked wonders for me.