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.
Related
Hello,
I own a Huawei P8 L09, bootloader unlocked, rooted and with TWRP recovery.
I tried this morning to flash a new rom using TWRP recovery.
Problem is that I do believe I wiped to many partitions and I ended up with a bootloop.
I could at first access 3 times the emui erecovery (btw, Wifi recovery failed) but not anymore (is it related to the battery level ? I don't know how much I still have)
Following a lot of threads here and on some other forums (I've been searching now for approx. 7 hours...) :
I downloaded a update stock ROM (B170 something), I extracted Boot, System, Recovery and Cust
I entered bootloader mode (it's the only mode I can go to; recovery No, Download mode neither)
and on my computer I typed in the cmd "fastboot flash recovery recovery.img" same with system, cust and boot.
All of them said "Okay" but the bootloop is still there and I can't acess any other mode or shut the device off.
Also, my bootloader indicate that i'm "unlocked" but when I try to do something as :
"fastboot erase cache" it says "remote: not allowed" or something like that.
I tried the SD card flash method but I can't even acess the 3-button mode (doesn't work - bootloop again).
Finally, I've got 2 questions :
1) Is there a solution ? Is there/was there anybody in the same situation ?
2) Does the battery level influence wether I may or not enter any mode ? like b.e. under 30% I can't access recovery or something like that ?
Thanks in advance for your help and sorry for my bad english.
Greetings from Belgium !
Jules
Hi!
I have the same situation as you do, All i know is that you can access the eRecovery only if you're plugged in.
But it's completely useless. Have you found any solutions yet?
Edit:
i struggled and i'm still struggling but i figured out that I need the recovery and boot img of the version i was on previously. In my case that is B350.
The main mirror is down but i managed to find another one: https://mega.nz/#!NAcgQY7Y!I4eRfkaq62J31csv_wZ8_nTzmUbWPX71JUicDysjus8
after flashing them i was able to partially flash (using vol+-&pwr) B170 (it only went up to 90% with my USB attached, fails without USB)
At my surprise it booted B170 even if it didn't complete, however right now it keeps rebooting every minute. I'll update if i manage to fix this
I have the same problem as you both. To flash boot.img and other files by fastboot we need to unlock bootloader. To unlock bootloader we need to have Imei, Product Id and SN, but I can't read it because phone won't turn on.
Anyone know how to get this info?
you can read these info from the packaging box!
I managed to fix my issues (i believe) by continuously flashing and flashing versions. I never really managed to fully OTA update to 100% due to some "CUST error" but from B350 i managed to "update" to B170, then to B200, then to B321a.
Now i just installed TWRP and rooted it and on the process of installing xposed (if possible).
I wasted a good 6-7 hours on everything already
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
TukAliveFra said:
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
Click to expand...
Click to collapse
you gonna pay for the repair..
Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.
Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.
Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again
Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.
Thank you in advance for any help you can provide.
I successfully rooted my Zenfone 3 Max (ZC520TL) using Magisk, but wanted to restore the phone back to its factory firmware. I used the uninstall option in Magisk but this reported that it could not find the backup boot image. Unfortunately I then made the mistake of following unroot steps on other sites rather than this excellent resource. Long story short I somehow managed to lock the bootloader again so when I try to use fastboot to flash any image I get the error "FAILED (remote: not allowed in locked state)".
When I turn on the phone, on the ASUS splash screen it says...
Red State
Your device has failed verification and may not work properly
Your device will boot in 5 seconds
… ie boot loop.
Q) What can I do to get my phone usable again? I searched this site and found lots of info on how to unlock the bootloader and how to root, but nothing about how to stop the boot loop.
I do have access to the Recovery mode and see options such as "Apply update from ADB" and "Apply update from SD card" but I am unsure if these will help?
Thanks again for any help and/or links to solutions on this site that I missed.
I was caught in similar situation, due to unsuccessful flashing using asus flashtool, I ended up flashing stock firmware (not the raw firmware) via recovery and everything was back to normal.
Thank you... but...
sanctitude888 said:
I was caught in similar situation, due to unsuccessful flashing using asus flashtool, I ended up flashing stock firmware (not the raw firmware) via recovery and everything was back to normal.
Click to expand...
Click to collapse
Thank you @sanctitude888 so much for your help. I'm new to rooting but keen to learn. What's the difference between "stock" firmware and "raw" firmware? For example I can download the device firmware from ASUS and extract the boot.img file (ASUS no longer provides the recovery.img file) but is this considered "stock" firmware or "raw" firmware?
You also mentioned you flashed via recovery. In Recovery mode I see multiple options such as "Apply update from ADB", "Apply update from SD card", "Mount /system", etc. Could you please be more specific on how you did the recovery please?
Thank you for your help.
Kind Regards
Sorry for very late reply. Despite useful guides are there, they are pretty much scattered. Few posts or threads I could suggest as follows :
1. https://forum.xda-developers.com/zenfone-3/how-to/updated-unlock-relock-bootloader-t3749456
2. https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-ze520kl-ze552kl-unofficial-t3738811
3. https://forum.xda-developers.com/zenfone-3/help/help-ze552kl-bootloop-flashing-t3820371
4. https://forum.xda-developers.com/zenfone-3/how-to/guide-how-to-root-zenfone-3-official-t3745650
About phone: Huawei P9 lite VNS-L21C432B161 (central Europe)
First modifications
A long time ago i unlocked bootloader and successfully rooted the phone. I turned off OEM unlock option in settings after rooting, because someone said i should do so for security. Then came EMUI 5 OTA. It somehow updated itself without me agreeing. Android nougat detected, that the bootloader was unlocked and so it assumed that OEM unlock option was also ENABLED when it really wasn't, making me unable to re-enable the option.
So i used the https://forum.xda-developers.com/huawei-p9lite/how-to/tutorial-rollback-n-to-mm-c432-devices-t3563955432-devices-t3563955" <-- official rollback package and installed stock ROM through dload.
Here is the part where i messed up horribly
Now i wanted to update to android 7 again, but updater wasn't giving it to me and i was unable to flash it through TWRP. I installed the rollback package again through download mode as it said it allows any ROM to be installed, hoping i could then install android 7 through Download mode, which would in turn allowed me to install newer version of TWRP to then install a nougat based custom ROM.
Current situation
Now i am stuck at the 'Your device has been unlocked and can't be trusted. TWRP 3.0.1 should be installed but it never boots. Can't access bootloader, phone doesn't seem to be detecting the Power+Volume down combination. Recovery gets stuck at the shorter warning screen during boot, erecovery gets stuck as well. This has been like this even before i tried this, no idea what caused it. I can't even access download mode, which gets stuck at the shorter warning screen as well.
What i hope to achieve now
At best: To make it work again.
At worst: To at least be able to turn it off somehow so the text doesn't get burnt into the screen in case i ever manage to fix it.
Thanks in advance
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Can’t post it in the developer forum for this device as I don’t meet the requirements for posting it
i.am.the.best said:
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Click to expand...
Click to collapse
1. 1st try to flash fastboot rom,
after install fastboot rom if the phone stuck on asus logo or any other error then
2.Try to install Qfll file (select ww_no_fsg.xml file) after successful installation , boot your phone.
3. again connect your phone fastboot mode and flash fastboot rom
If every installation is successfully done then i am sure that your phone is boot properly in stock rom with lock bootloader.
because I faced same issue,
remember 1st try to install stock fastboot rom and then try to flash Qfil files
Wish you good luck :good:
Try flashing fw063 before flashing your custom rom.(that fixed for me)
if it didn't work try this (rooted):-
https://forum.xda-developers.com/showthread.php?t=2522762
Thanks bro. I have successfully unbricked my mobile