Database Users

Softbricked phone, no idea how to proceed

EDIT:
It seems since there is no Huawei P8-Subforum, my thread seems to has been postet to misc. Development. Im sorry about that!
Hello there,
I spend the last three hours trying to get the device (L09) to work again. I made the terrible mistake to update my phone with custom recovery (TWRP) installed. My target is to upgrade from B191 to Marshmallow.
The main probleme here is that I don't own a micro-SD card plus the internal storage contains a dload-folder which I can't delete.
My current situation:
- The phone is bootlooping at bootanimation
- I can access the fastboot-mode, stock-recovery and upadte-mode
- My internal storage (intenal SD-Card) contains a folder named "dload" with the B200 firmware
- I flashed the stock B200 recovery.img and boot.img (extracted with Huawei Extractor)
- When going to update mode the phone proceeds to 5% and then shows "Software install failed!"
I don't really know how to proceed from here on. I tried to flash TWRP again to clear the dload-folder and place another firmware, but somehow twrp can't be installed anymore - flashing shows "OKAY" but when booting into recovery, the same old Huawei recovery is booting. Also I'm confused as to when to leave the USB plugged in or disconnect it.
My current plan is to revert to 170 firmware to start completely over. I downloaded the 170, 200 and 313 firmware.
How to proceed?
EDIT:
I flashed recovery.img, boot.img and system.img from B170 and now the boot repeats at the Huawei logo. After flashing boot.img and recovery from B200 I get to the bootlogo again, which is stuck.
Solution:
After flashing boot.img from B191 the B170 firmware booted successfully. I got a few random reboots at the start, but they quickly grew less and now I have a somewhat stable B170.
Upgrading to B191 or B200 didn't work, tho. I'm trying to get behind that now.

s7 edge freeze at samsung logo

hi guys.
My problem started few days ago when my phone start to restarts many times in a day,so I start to do a factory reset and it failed,I mean the phone restart like normal after this attempt but have some errors with google play services and the phone starts to booting again and again..after this I managed to get in the recovery mode and try to do a factory reset there but failed again and the phone start to boot to Samsung logo..I put it in download mode and try to flash with odin the latest firmware noughat that was previously installed in the phone 2 weeks ago..the odin process starts normaly and it was a successful operation but I got a error about NO COMMAND and the phone is restarts to Samsung logo..What can I do to fix this issue???

try to flash back an 6.0.1 version, after make wipe data from recovery and let phone reboot and see if anything changed, if same result you might have a hardware issue

remosam said:
try to flash back an 6.0.1 version, after make wipe data from recovery and let phone reboot and see if anything changed, if same result you might have a hardware issue
Click to expand...
Click to collapse
to flash back to 6.01 version I have to download this?the problem is that now I don't have good internet ...If I didn't enabled the OEM unlock and usb debugging before the flash,could be the cause for this boot logo?

cristy7610 said:
hi guys.
My problem started few days ago when my phone start to restarts many times in a day,so I start to do a factory reset and it failed,I mean the phone restart like normal after this attempt but have some errors with google play services and the phone starts to booting again and again..after this I managed to get in the recovery mode and try to do a factory reset there but failed again and the phone start to boot to Samsung logo..I put it in download mode and try to flash with odin the latest firmware noughat that was previously installed in the phone 2 weeks ago..the odin process starts normaly and it was a successful operation but I got a error about NO COMMAND and the phone is restarts to Samsung logo..What can I do to fix this issue???
Click to expand...
Click to collapse
flash 6.1 firmware via odin

cristy7610 said:
to flash back to 6.01 version I have to download this?the problem is that now I don't have good internet ...If I didn't enabled the OEM unlock and usb debugging before the flash,could be the cause for this boot logo?
Click to expand...
Click to collapse
oem unlock and usb debugging is only related to custom firmware or rooted stock, isn't your cause. download stock 6.0.1 and check what happens after flash

riz157 said:
flash 6.1 firmware via odin
Click to expand...
Click to collapse
On first flash today via Odin I got a message "no command" and android screen,if it means something that...If I use smart switch and the option emergency software recovery ,it will download the original 6.1.0 firmware?

"no command" mesage usually appears before entering recovery mode, use smart switch and enter serial to restore firmware, will install 6.0.1 if your original csc don't have yet 7.0
---------- Post added at 11:38 PM ---------- Previous post was at 11:30 PM ----------
if you have international model, G935F you can download XEU 6.0.1 firmware from here: https://drive.google.com/file/d/0BzcqBQZhElPfNDJzMTd5NGh6ODQ/view?usp=drivesdk

Thanks guys..I managed to fix it with smart switch...and after this I flashed via Odin,noughat again and everything is ok now.

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:

[Magisk&rooted] MI A1 bootloop after trying to install updates

The phone worked great with Magisk and Oreo android, a few weeks ago there it started to download an update, but I paused it very quickly and canceled OTA, it was only in the begining of stage 1/2..
Today I followed this recommended GUIDE in order to update the device
What did I do wrong here?
1. in magisk >uninstall>restore image
2. enabled ota and started the update (continued from about 10% downloaded since it was paused weeks ago)
3.When stage 2 of the update started, in Magisk Install → Install to Second Slot, some commands ran on a black screen..
4.then I clicked reboot (sine the guide doesn't mention what to do), should I have clicked close instead?
Click to expand...
Click to collapse
Now it's stuck on boot
I managed to turn it off for now via the menu that you get by holding power+up
What should I do next? I installed this program, is it useful to fix the phone ?
Thanks

Fixed without deleting anything this is what I did (huge thanks to https://forum.xda-developers.com/member.php?u=5258176 )
1.enter fastboot on the Mi A1
2. Download this extract the folder "tissot_images_V.9.5.10.0.ODHMIFA_8.0"
3. install XiaoMiFlash
4.choose "save user data"
5.Select the folder and flash..
6. wait a few minutes for it to run, and it's all perfect, the phone starts with everything installed just like before the failed update with android 8.0.0
I'll never OTA with magisk/root

[Solved] Lineageos downgrade to Stock Android7. Bricked, I can only see logo LGU+

Hello.
I got V20 F800L "rooted" with Lineageos. I wanted to restore the factory system. I downloaded the .kdz file and LGUP and LGFirmwareextract program and started flashing.
During the final phase of flashing, the smartphone resets, then less than a second I see a circle with the word "erasing", then a moment animated LG logo, then the static logo LGU+ and locks here.
Windows drivers and LGUP still recognize the device, I can flash different versions of f800l, I tried 10e and 20k and the program communicates that the flash was successful but nothing changes, the system does not boot.
I can enter the "power + vol + down" mode to do "factory data reset", after that appears for less than a second a circle with the word "erasing" , then logo "LG U +" logo and locks in place.
How to recover the device, please help.

Use LGUP patched, restore device with DL Mode option and select all partitions. When device rebooting, disconnect and reconnect the battery then do the factory reset. Your device will be fully restored to stock

khtr98 said:
....then do the factory reset. Your device will be fully restored to stock
Click to expand...
Click to collapse
Thank you for your response.
I tried to use the version with the LGUP patch.
I chose the PARTITION DL option and selected all partitions. While the LGUP program reset the device, I pulled out and inserted the battery, after the reset the program confirmed the success, but the device still can not start, and then all I have is the LGU + logo.
Did I do something wrong? do you have any other ideas?

I have no idea, maybe some partition is corrupted and cannot be restored.
But you can try this tricky way (if you have no choice)
Download us996 10f kdz, use PARTITION DL with all selected partition to crossflash your device to us996. LGUP will show a dialog box tell you want to repartition some partition layout. Click yes then wait to finish and hopefully it boots fine.

khtr98 said:
I have no idea..
Click to expand...
Click to collapse
I tried with different versions of ROM. Finally it boot. At the beginning I flashed with versions 10e (Android 7) and 20k (Android 8) with PARTITION DL mode, but it did not boot, but finally I was flashing the latest version 30e (Android 9) for F800L and the system started
Thank You khtr98. Problem solved

khtr98 said:
I have no idea, maybe some partition is corrupted and cannot be restored.
Click to expand...
Click to collapse
But option to enter the download mode (via usb+volume-up) has disappeared. I lost possibility for downgrade and root when I choose android 9 for f800l ?

after upgrade (official android 9 for f800L), when i try to go back to oreo or nougat i used a patched LGUP i get the message:
Error 0x ....., plaease use last DLL
LAF Protocol Version is not match DLL = 10 .......
Device = 14 ....
is downgrade possible?
ok. is possible
==================================================
For educational purposes, I again downgraded the version from the rooted line 17 to the factory Android 7.
This time it went smoothly because I did advanced cleaning in TWRP before.
I used the wrong version of the patched LGUP, this version is correct, it allows downgrade: https://forum.xda-developers.com/android/general/tecknights-aristo-2-tutorials-t3805141/page3