Database Users

Huwei P8 L09 stuck in bootloop many tips tried, none worked

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..

Asus Zenfone Max (ZC550KL, Z010D), Android M, Unable To Unlock Bootloader

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.

I think I brinked my phone. Please help [SOLVED!]

Hello. I tried downgrading from the latest ASUS firmware to Android 6.0.1
I used this tutorial to install the raw firmware: http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html
Went all the way to the last step when the app hanged. ASUS Flash tool went all the way saying
Code:
Run flash image script ...
It was hanged there. And as per this video, went all the way to the end where it showed the "code bar" on the right (https://www.youtube.com/watch?v=P8xg7A-P7Ak)
This is when the "Android" uninstalled driver showed up in Windows. This is under "Other devices - Android". I tried updating this driver using the ASUS_Android_USB_drivers_for_Windows found here: https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_Download/ but it wouldn't install the drivers.
Note that I used these ASUS USB drivers to get the ASUS ADB Interface installed. As per the tutorial I showed in the very first paragraph, I never got the "ASUS Android Bootloader Interface". This is what I think this "Other devices - Android" is found under Computer - Manager - Device Manager.
Most tutorials on the internet shows that the "ASUS Android Bootloader Interface" should be installed using these drivers found on ASUS website, the ASUS_Android_USB_drivers_for_Windows.
Now of course because I unplugged the phone, it will continously stay on the Android splashpage showing the loading circle infinitely.
As a last attempt I tried installing the "stock", not "raw" firmware (the one I wanted to install WW_13.16.5.49 but ASUS would not let you downgrade using the recovery "power+volume down" and using "Apply update from microSD card". It would give the
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
)
Well, after it brinked, I tried it again and this time it DID install WW_V13.16.5.49. Was succesfull. But after the ASUS splashscreen it's still stuck in the booting process.
I am very sorry if my post is convoluted but I tried explaining everything I did. Any way to un-brink it? I think maybe if I figure out how to properly install the ASUS Android Bootloader Interface, I can try again ASUS Flash tool and install the raw image and maybe that will fix it?
Please help. Any questions if my thread is too confusing, please let me know and I will answer it. I can't even turn off the phone. While it's stuck into the load splash screen, if I press the power button it just restarts, not turn off.
I still have access to fastboot (pwr + volume up) or recovery (pwr + volume down)
EDIT: Phone won't get recognized anymore in ASUS Flash Tools. Serial number won't show up to select

Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.

wang1chung said:
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
Click to expand...
Click to collapse
Thank you, this actually worked!!
Aaaand, it's actually on the version 13.16.5.49!!!! THIS IS EXACTLY WHAT I WANTED!
So apparently by brinking my latest nougat 7.0 update from ASUS via the ASUS Flash Tool trying to flash the .RAW 13.20.10.137, the standard recovery system (power+volume down) allowed me to install the 13.16.5.49 version. Then I assume remnants files didn't allow to properly boot, and your idea to wipe cache and factory reset fixed that!
What is so great is that I was scared that because the .RAW firmware was newer than the version I needed (13.16.5.49), I wouldn't have been able to install it. It was the same problem initially, when I tried to install 13.16.5.49 directly via recovery over the latest nougat 7.0 version from ASUS, but it was giving me
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
I think this error was due to the fact that ASUS won't allow older firmwares to be installed over newer ones, as per their webpage
https://www.asus.com/support/faq/1009748
Code:
You can not change the SKU from one to another, e.g., WW -> TW, and also can not downgrade your firmware, e.g., V2.20.40.13 -> V2.19.40.18
So in the end, what allowed the 13.16.5.49 stock firmware to be succesfully installed? The installer not detecting a proper firmware anymore because of the damaged update due to ASUS Flash Tools hanging because my computer won't install ASUS Android Bootloader Interface?

Glad you got it going :good:

Possibly Dead Device? [P8/P9 Lite (2017)][PRA-LX1]

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.

Unable to boot - Oneplus8 pro

Hi Everyone,
I have an issue with my Oneplus8 pro and below are the details
1. The device was working perfectly. I was interested to root the device and install a custom ROM.
2. The method used was to try and flash a patched boot image for the device but I think i landed up using a wrong boot image file.
3. The OS was on 10.5.10 if I remember correctly. I used a patched image file I suppose of an older firmware. Now restarts and goes to "QUALCOMM Crashdump mode". The only options are
a. reboot to fastboot mode
b. flash the TWRP for Oneplus 8 pro but that doesnt mount by storage so cant really transfer anything to flash again.
Requesting some help to fix the issue and apologies if i have not explained correctly.

Tried booting a stock boot image?

neverborn said:
Tried booting a stock boot image?
Click to expand...
Click to collapse
Hey,
Thank you for a quick repsonse. Yes, i had tried doing that and still the same error however while we speak, i just downloaded the msmDownloadtool and tried using it to flash a stock firmware and finally, i am so happy to see the device boot sucessfully
Thank you once again for tryin to help
Regards

Hello.
Clarify exactly how the procedure took place