Hej,
I recently got hands on my sister's old phone which had a broken touchscreen - I fixed that hardware issue, but now it seems I messed up the software?
1.) It's a P8 lite (2015, ALE-L21) DualSIM, which ran the latest OTA update (I think 4.0.3 or 4.1.3? EMUI)
2.) I followed this method to unlock the bootloader
(https://forum.xda-developers.com/p8lite/general/alternative-method-unlocking-bootloader-t3799294)
3.) that included a rollback to B170 (Android 5, EMUI 3) and rooting with KingRoot
4.) I planned on flashing TWRP, but the phone did not start into the newly flashed recovery, but into the Huawei eRecovery
5.) So I assume that it reinstalls the original recovery upon reboot, I tried to flash twrp again, but whenever I use the button combo (Volume Up+Power)
--> it does show me the red Huawei logo, but afterwards the phone is "on, but unresponsive",
having a dark screen, but the vibrating motor works whenever I touch the bottom row of the screen (where usually the navigation buttons are)
6.) Then I told myself, if I cannot flash twrp, I'd at least try to at least get the latest firmware (B620) installed again,
but neither the local update option nor using the buttom combo for dload works,
instead it has the same issue as described in 5.), going through the restart sequence with the huawei logo, but then being dark with vibrations
Did anyone have similar issues (see especiall point 5) and can help me out?
It's in a state of kinda working (having a usuable, but old firmware), but the restarting seems to wrong and everything that needs a restart (going into recovery, installing local dload update) seems to be messed up
I got it working somehow,
the twrp recovery I used might have been bad, so instead I used the one in the LineageOS14 thread.
When I tried to dload with the *#*#2846579#*#* sign combination, it finally started int TWRP
Flashed latest firmware, did backup (just to be safe this time...)
and now am using AOSPA without the issues described in 5.)
Related
I have rooted the phone and was using a custom ROM from meticulus.co.vu as well as his custom twrp.
I have the VNS-L31 variant.
I wanted to roll back to stock because the fingerprint sensor didn't work due to me not clearing the saved ones when I changed ROMs.
What I did was factory reset the device, flash stock recovery, cust and boot (from update.app) onto the phone and then put update.app into the SD card in a dload folder. I then proceeded to hold the Vol+, Vol- and Power buttons to update manually. This didn't work because it said 'Software install failed'. Now the phone only boots into eRecovery and fastboot. I cannot get into TWRP despite flashing it multiple times through fastboot.
I am completely out of options, please help me xda.
EDIT: I managed to get it working - for those with a similar issue - download firmware finder and go through ALL of the models, one will work!
However, I cannot sign into google play...
Maybe this helps? http://www.techoxygen.com/bypass-google-account-unlock-frp-huawei-p9-lite-nexus-6p/
Hello everyone,
I own a dual-SIM P9 lite (VNS-L31), which was rooted and flashed with TWRP with EMUI 4 (MM).
So yesterday I wanted to do the pending OTA Update, so I unrooted, reflashed it with stock MM ROM (I did not know that it was possible to update manually) and did the pending OTA-Update to B160, then unlocked the bootloader + rooted again and installed TWRP Recovery.
However, it was still on EMUI 4, so I downloaded the Dual-Sim-C432 OEMinfo and flashed it in TWRP, then I did the OTA Update to EMUI 5.
TWRP Recovery would not load up anymore, so I flashed revolution recovery.
Then I looked for a way to root EMUI 5 Nougat and stumbled upon the "Elite Kernel" in xda-Forums, downloaded it right away and flashed with Revolution.
It all seemed to work fine, Superuser worked as expected.
However, today my screen suddenly turned black. I hard-rebooted and it did not show anything (no bootlogo or anything) , but apparently it booted up the OS as I heared the sounds of incoming messages.
I once got into recovery, but the screen is still black (I only knew because revolution recovery lets the user mount the device in MTP and makes the cust drive visible)
When I plug it into my PC it plays the charging sound and opens up the virtual HiSuite CDROM and an empty MTP device (as it is needed to accept a dialog to grant MTP access)
Everything OS-related works (it played the alarm clock this morning and I was able to dismiss it by swiping, I can hear messages, once it played music as i tapped somewhere on the lockscreen)
sadly, USB-Debugging is not enabled (adb devices shows my P9 lite as unauthorized)
Sometimes the backlight flickers randomly, but the screen stays black
Sometimes the screen turned on again after pressing random buttons (either volume+ and - at the same time while on lockscreen or pressing the power button repeatedly), either behaving normal or showing a weird glitched picture.
I already tried getting into fastboot mode, my PC recognizes the device with serial number when typing "fastboot devices", on both my linux and windows system. I tried to flash the following:
boot.emmc.win from an TWRP Backup
system.img from the Huawei Extractor, extracted from the newest Nougat EMUI update.app
putting an update.app in the dload folder, booting the device up with the 3-button-method. It did not show the EMUI eRecovery screen, I left it for 10 minutes but nothing changed
boot.img, recovery.img, recovery2.img and system.img from the Huawei Extractor, nothing changed
Any Ideas on how to recover?
Thanks in advance and sorry for my bad english
Hi guys,
Yesterday, I unlocked my Huawei P9 Lite with the given code from EMUI, then I installed TWRP (twrp-3.1.1-0-venus.img) and installed SuperSU. All went okay, i managed to delete useless system app, but I realized i did not pass Safetynet Check anymore (and since i'm a PoGo fan..), so I uninstalled SuperSU and tried with Magisk, same issue. I uninstalled both, and couldn't get back the clean safetynet check.
There, I tried to install a official ROM for VNS-L31 xxxx361, but I did it wrong and the whole thing crashed. Now i'm left with no OS, phone is bootlooping for ever. The only things I can access if TWRP and Fastboot mode. I tried to flash img from a huawei release, but i get this error that scare everyone i asked about : remote : sparse flash write failure.
I've no idea how to not trash my phone and go grab another one if I ever want to make a phone call again!
Please help!!
Kindly,
Antonin
I had similar problem but I had no recovery just eRecovery and fastboot (which didnt let me flash anything).
Download FULL rom from:
hwmt.ru/oth/HWFF/info/view.php?find_model=VNS
(sorry cant post links)
Make sure u choose right model and location.
Extract the update.app and put it on sdcard in folder named dload, insert that sdcard into the phone.
Boot to erecovery and shut down the phone from there, then turn on the phone with both volume buttons pressed and wait till the rom will be installed.
If you didnt success to boot with vol + and vol -, try to press power wait for vibration and quickly press both volume buttons and hold.
LATE EDIT: solved, read bottom of this topic for solution
Hi, so I have a P8 Lite and after properly unlocking the bootloader, I flashed TWRP (versions/ports found on XDA for P8 lite).
After using fastboot fastboot flash recovery twrp.img properly, it outputs OK, indicating it successfully flashed.
Now, assuming all went fine, I tried booting into recovery with powerbutton and volume up, after a few seconds only it turned off, the whole device just shuts itself down.
I then noticed it'd go into Huawei eRecovery when you keep holding it, so I just briefly pressed both keys until it started up, immediately released, and it still failed to boot into recovery.
To make sure I made no mistakes with triggering the recovery boot, I used adb to perform ''adb reboot recovery'' and so it attempted to boot into it, resulting yet again in the same black screen shortly after the Huawei (powered by android) logo, where that black screen is actually the device shutting itself down.
So the conclusion I draw is that the recovery is broken after installing it, the question is how. I'm not a novice to this kind of stuff, as you might have noticed, but still I cannot think of what went wrong, as my bootloader is successfully unlocked through the EMUI method, and I made proper use of fastboot to flash recovery, after which it tells me it succeeded, using the proper recovery for this device.
To double check I also installed the CWM recovery released for the P8 Lite (https://forum.xda-developers.com/p8...overy-clockwork-mod-recovery-cm-12-1-t3342209), as TWRP's for it (multiple versions/releases..) failed thus far, and also with CWM the same happens.
I really want to proceed flashing recovery to then root the phone and install a custom ROM, so any help or ideas what the cause might be, will be appreciated, or anyone that encountered the same problem!
SOLVED (was too lazy to post on time, i fixed it shortly after posting this).
The problem was that I flashed a bad recovery, basically the ALE-L21 has different TWRP versions advertised in the P8 lite section, i happened to choose a not too good one, it may have even been one that didnt belong to my model (like P8 lite generation year), not sure as the section is co-shared between P8 lite model generations, this mistake is easily made.
If you have this issue, just keep trying additional (TWRP) recoveries, the subsequent 2 versions from different publishers that I tried were working fine and the issue stopped.
Hi,
Today I tried to install LinageOS 17.1 on my Huawei P10 lite (at start, still completely Stock Rom).
Unlocked bootloader following procedure in https://forum.xda-developers.com/p10-lite/how-to/p10-lite-bootloader-unlock-june-2020-t4113315, worked great.
Installed TWRP following https://forum.xda-developers.com/p10-lite/development/recovery-twrp-huawei-p10-lite-t3953890 ; also here, no problem.
Then I tried installing LinageOS following this thread https://forum.xda-developers.com/p10-lite/development/rom-lineageos-17-1-huawei-p10-lite-t4064115 . Here I ended up with the Linage OS System UI that constantly crashes, restarts, crashes again etc.
This problem is mentioned in the same thread but none of the solutions seems to work for me.
I tried to downgrade the TWRP to the older 3.3.1 and then redo the entire installation procedure => No success
Then I tried wiping and formatting all the caches/data that was mentioned during the thread + re-executing the entire installation procedure => Still no success.
Can anyone help me?
What could also be relevant:
In TWRP I cannot seem to copy data to the device, whenever I try to do that via the File Manager (I am using Linux Mint 20) I can see the device and its internal storage but transferring data is horribly slow (it would take 5 hours 45 minutes to transfer a 3 MB file) or just fail. I also tried this in a (virtualized) Windows 10 installation with the same results.
When earlier today (before having installed LinageOS) I tried to transfer files, it worked very well. Also, I tried it with multiple USB cables just in case it might have been a faulty cable.
Pushing a file via adb push doesn't work as the device shows up as "unauthorized". The installation of the patches (magisk, los_patches_warsaw, opengapps etc.) I did using ADB Sideload which seemed to work nicely as well - really making me thing that the USB transfer issue is not hardware-related...
Furthermore, I know this is a noob question but anyway: the procedure says "flash los_patches_warsaw.zip". How exactly should this be done? Copying the file to the internal storage from a PC (which I cannot do, see above) and installing it via TWRP Install? Flash via Fastboot (to what destination)?
Tx in advance!
I've had this issue as well, what I did was disabled dm-verity and forceencrypt using https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 after flashing system in fastboot and then I flashed los_patches_warsaw.zip from SD Card (MTP is broken in older twrp, use 3.4.0, also try this at your own risk).
Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?
Bart80TR said:
Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?
Click to expand...
Click to collapse
I think it's only possible by dirty flashing it, also a little correction for my last post, I meant internal storage not micro SD card.
it's a shame the original LOS 17.1 thread is closed.
My experience with WAS-AL00 (china version) on macOS:
After I flash LOS 17.1 ROM, "fastboot reboot recovery" doesn't reboot the device into recovery. Then I unplug the phone, and reboot into system, I came across system UI crashing constantly. After managing to get through to the main screen. Plug the phone, "adb reboot recovery", then flash los_patches_warsaw from microsd card (you need to copy the file to a microsd card and insert it into the phone). Then reboot system, this time the screen is black. only long press power button show three options "power off", "restart", and another one i don't remember. @KinteLiX 's method didn't work for me.
Then I tried stock recovery with openKirin (worked), Twrp 3.4.0.0 with openKirin (also worked, even though they state that only stock recovery works with their ROMs).
Last I tried twrp 3.4.0.0 with AOSP 10 from @DarkJoker360. It works.
Note: after flash the ROM, power off the phone, and long press three buttons volume up, volume down and power at the same time, and you will boot into twrp. If it shows update fail, then reboot and try to get into erecovery and wipe data/factory reset and then power off, long press three buttons simultaneously and you will be able to boot into twrp, if not, wipe data/factory reset again in erecovery (I accidentally found out about this. before this I was unable to boot into twrp after flashing any ROM, "fastboot reboot recovery" doesn't work). then do as the thread shows.
update: making a call doesn't work with AOSP 10 on my device.
The system crashing should come from the integratet AOD overlay....there should be a solution to solve that issue but i didnt rember the correct way how to. Just search in the p10 lite forum here on XDA.