Hi guys.
I have a Huawei P8 Lite 2017 PRA-LX1 Single Sim, no brand EUROPE [PRA-LX1 8.0.0.400(C432)].
Yesterday, I suddenly had an idea: unlock OEM (I have a code from before Huawei stopped giving them),
flash TWRP, Magisk, then root and finally flash an official DotOS 3.0 Build for EMUI 8 devices
(all packages built for prague devices like my one). So I searched through XDA and other forums to find TWRP and
other necessary files (all listed here):
• TWRP Recovery: Google Drive "TWRP 3.2.1-0 April 8th build Round 2.img"
• Magisk - that's useless to list - both APK to install and .zip to flash via TWRP: Apkmirror
• Custom ROM: xda-DarkJoker360 "Dot OS P v3.0 for Huawei P8 Lite 2017"
• GApps: OpenGapps ARM64, 9.0, nano
So i unlocked the bootloader using the adb commands everyone knows.
I flashed TWRP using this guide: https://www.youtube.com/watch?v=ijAuoxlnzlo (I'm italian).
From the phone I downloaded Magisk Manager, installed, then from there I downloaded the flashable .zip.
I flashed the Magisk .zip from TWRP.
I checked the root status with Root Checker App: phone was rooted.
I moved the flashable DotOS ROM .zip and the GApps .zip to a 15GB non-formatted SDHC.
Inserted the SD in the phone.
From Magisk Manager i rebooted the device in TWRP Recovery mode.
Followed the "CLEAN FLASH" instructions from the DotOS thread:
Code:
• Download the latest build and GApps
• Reboot to recovery
• Make nandroid backup (Not Necessary)
• Wipe System, Data, Cache, Dalvik
• Flash the latest build and GApps
• Reboot
- I tried to do a Nandroid Backup, but since TWRP didn't want to do it (I was getting errors), I continued without backup. (FIRST MISTAKE)
- I did the Wipes, but there was problems with the Cache wipe: "Failed to wipe cache" or something like that.
So I looked for a solution in XDA, and i found something like "Do a data format since the datas are Encrypted"
- I did the Data Format
SECOND MISTAKE, because the Format deleted the stock OS, and I had not yet flashed the custom one (DotOS).
- It rebooted in TWRP and i flashed DotOS and GApps. I did another Cache and Dalvik wipe (THIRD MISTAKE)
and i rebooted.
- I saw the beautiful DotOS bootanimation playing on the screen, but then..
- the screen got black, and the Huawei logo appeared. I had an heart attack.
- The black screen with "Your phone is unlocked and can't be trusted" and the three options appeared.
I turned off the phone.
Now this is my current situation:
I turn on the phone
- The black screen with "Your phone is unlocked and can't be trusted" and the three options appears.
- If I let boot, the bootloop goes in action (DotOS bootanimation -> Black Screen -> Huawei Logo -> "Your phone is unlocked" screen again)
- If I press Vol+ for more than 3 seconds, the phone boots into Huawei erecovery. Now from there i can:
- "download the latest firmware and recovery" but it fails at 5%
- Do a factory reset. I have to type "yes" to confirm. Then it shows a "Your phone is unlocked" screen but without options for a while, and
then, without doing nothing, it boots into TWRP
- Reboot (bootloop goes in action)
- Shutdown
So, what do i have to do? That's my only phone (don't ask me "so why did you decided to do this", i know already).
If you have any solution, and maybe you had a similar experience, please (PLEASE :crying tell.
Thanks in advance.
Related
Thanks a Lot.
Can anyone help me with fresh os installation. TWRP seems to be crash/rebooting to itself. I have builds of miui Lineageos and resurection remix on my sd card along with gapps nothing is working (getting installed).
The TWRP recovery goes into self loop once I swipe to install (OS + Gapps pico). It asks me to leave the partition unmodified again and again. I check the box that says :
" Never show this message again" every-time.
But it keep crashing/ coming back to main menu. There is just a black screen in the transition and even the MI.com logo does not appear.
I have tried TWRP 3.1.1.0 and went all the way down to 2.8. Same story.
I do not have any OS cause I deep cleaned in the middle.
(Device is unlocked I started with a rooted miui 8)
Please! Help!
Hi,
I am new to XDA, and I have an issue with my P9 lite VNS-L31 single sim
I just wanted to root it,
I unlocked the bootloader, install recovery and install root package via recovery
The problems begun when i tried to enter developer options, security settings, fingerprint settings and lock screen settings, everytime i click that button, THEY CRASH,I have a branded version, so I wanted to unistall some brand bloatware
(not system apps) everytime i uninstall an app, it soft reboots itself and app does not get uninstalled, so i tried to flash elite rom
-Installed elite TWRP
-Format Data
-Wipe data
-Flashed the zip file
no success, bootloop
tried to use the 7Slevin Debrand method to get back to stock rom but when in wrote "fastboot flash recovery twrp.img" and rebooted to recovery… or at least tried to boot into recovery because everytime i try entering recovery, it gets stuck on "Your device is booting now…", so it was there that I understood i was doomed, NO RECOVERY NO FASTBOOT an the Elite rom started looping, while booting it forcereboots itself into eRecovery
Can someone please help me?
Thanks in advance
Thread closed per OP request.
Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore
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.
Hi all,
So I was triying to update my Magisk through the recommended direct update method. I got a bootloop. Never had any issues with this update method, Magisk always did a splendid job.
Now my only options are:
1. Flash a custom rom (I don't have any stock Telekom roms)
2. Update Android OS to 8.0 with LG Bridge (my goal is to have a stock rooted android os, that's why I'm doing this)
3. adb reboot, flash the latest twrp recovery (at least that's working)
4. flash the latest Magisks without reboot option, just power off and then turn on. And this is stage where I get a bootloop.
I only have v19.3 saved on my HDD. Flashing that is working just fine, not causing any bootloop. However Fake GPS and Pokémon Go are not working with this version anymore. :/ So I'm kinda chess-mated here because of this Magisk bootloop.
Anyone can help me how can we fix this?
I have bootloops with all Magisk 21.x versions, so I'm stuck with 20.4. Can't you download Magisk 20.4 and install it from TWRP? I don't need SafetyNet, so I have no idea if Magisk 20.4 can still pass the check, but at least it would be newer than Magisk 19.3.
I downloaded the previous 21.0 versions from here https://droidfeats.com/download-magisk-zip/ flashed it and it's working. I also tested the previous versions. Seems like only 21.4 version is affected only, which is the latest stable.
I had the same problem: I had Magisk 21.4 and withing Magisk Manager I tried to update to v. 22.0 because I got an update prompt that asked me to do so. Trusting everything was fine I updated but I got a bootloop. I managed to recover from bootloop and get the latest version of Magisk working in my Huawei Y5 MYA-L13 (Android 6.0). For these steps, it is assumed Magisk v21.4 and Magisk v22.0 ZIP files are stored in your storage. This is the way I did it:
Manage to get into stock recovery mode.
This step was more time-consuming than it should have been... This Huawei model with the bootloader unlocked states at boot: "Press volume key up to 3 seconds to enter recovery to restore your device". It didn't... With Vol+ just restarted the device (no TWRP or stock recovery or download mode...) and pressing Vol- it loaded into the bootloop. It took me some time to guess the right way:
Plug the turned-off device into a USB cable plugged into the computer.
Wait for the device to start into "charging mode" (I made up this... I mean wait until the charging percentage appears).
Turn on the device using the Power Button.
Immediately, press and hold Vol+.
The device will reboot. Press and hold Vol -.
The device will get into the stock recovery mode (EMUI Huawei eRecovery).
Try again if this fails... After a few attempts, you'll get it.
Now the device will be visible to ADB. Verify this in a command prompt with adb devices. Mine was listed as 0123456789ABCDEF recovery.
Use the command adb reboot recovery to get into the real recovery mode. I mean TWRP. (It's still there even if it seemed to be it wasn't).
Flash the version that caused the problem. In my case, I had Magisk v21.4 initially, so I installed this same version ZIP I got from the official Magisk GitHub releases section.
Once finished the installation, if it was successful Reboot. The device should boot normally this time, having installed this version of Magisk and not the new one, of course.
Now proceed to uninstall Magisk 21.4 completely using the ZIP file provided in the above URL (step 4) with TWRP.
Follow the official installation guide in the Custom Recovery section to install Magisk 22.0 (that is: having renamed Magisk-v22.0.apk to Magisk-v22.0.zip previously, use TWRP to install it). Reboot.
Your device should boot normally. You'll find a Magisk app where you'll be able to verify latest Magisk 22.0 was successfully installed!!! DONE.
I hope my guide is useful to someone. If so, please like my post to be aware it was useful. Greetings!
TL;DR
adb reboot recovery
Install Magisk-v21-4.zip. This solves bootloop problem!
Uninstall Magisk using Magisk-uninstaller-20210117.zip
Rename Magisk-v22.0.apk to Magisk-v22.0.zip. Install it using TWRP.
Reboot. You have the latest Magisk version v22.0 installed with no bootloop!!!
I've upgraded from v20.4 to v22 yesterday using the new Magisk app, it all went smoothly.