bricked p8 lite 2017 - P8 Lite (2017) Discussion

I flashed RR 1 hour ago on my pra lx1. everything was working, but i the phone is my old phone and i want it to give it to my dad. RR is easier than emui and i just wanted to try it out. I resetet the device, but my twrp is for android 8 and twrp doesnt work its just stuck in loading screen. I flashed another twrp but it doesnt boot as well. And now the deivce boots only in recovery, but the recovery is stuck in loading screen.
I can acess adb commands, but sideload command doesnt work
Anyone got an idea?

TheDarkMadness said:
I flashed RR 1 hour ago on my pra lx1. everything was working, but i the phone is my old phone and i want it to give it to my dad. RR is easier than emui and i just wanted to try it out. I resetet the device, but my twrp is for android 8 and twrp doesnt work its just stuck in loading screen. I flashed another twrp but it doesnt boot as well. And now the deivce boots only in recovery, but the recovery is stuck in loading screen.
I can acess adb commands, but sideload command doesnt work
Anyone got an idea?
Click to expand...
Click to collapse
Remember mate, don't use TWRP to wipe data/ cache.
Follow this guide to restore your device and download your own device's Firmware
https://forum.xda-developers.com/p8...uide-brick-huawei-p8-lite-2017-maybe-t3816694
Always wipe cache/data via Erecovery

Related

NEM L-21 Bootloop

After unlocking my bootloader on my NEM L-21 I installed TWRP too, it all worked fine and well and then I decided to flash a CM13 ROM, before doing that I wiped my cache and userdata, I tried flashing it but then it threw me errors about not being able to mount /cust, I decided to restart it and leave it for later but now after restarting I can't boot into my system.
It restarts by itself if I try booting into the system, booting into the erecovery is useless since it cant find a firmware for my phone to download, and whenever I try booting into TWRP it gets stuck on a screen with "Your device is booting now...".
Any ideas on how to access TWRP or possibly flash the stock rom? Fastboot refuses to do it.
PraiseTheFiddle said:
After unlocking my bootloader on my NEM L-21 I installed TWRP too, it all worked fine and well and then I decided to flash a CM13 ROM, before doing that I wiped my cache and userdata, I tried flashing it but then it threw me errors about not being able to mount /cust, I decided to restart it and leave it for later but now after restarting I can't boot into my system.
It restarts by itself if I try booting into the system, booting into the erecovery is useless since it cant find a firmware for my phone to download, and whenever I try booting into TWRP it gets stuck on a screen with "Your device is booting now...".
Any ideas on how to access TWRP or possibly flash the stock rom? Fastboot refuses to do it.
Click to expand...
Click to collapse
Download the official firmware. Extract it using "huawei update extractor". There u will find recovery. Put ur phone in bootloader mode, by volume - & power button. Flash the recovery. Put the dload folder in ur sdcard. Then by the three button procedure, flash it.

[URGENT] Stuck in Bootloop. Help.!!!

I was on MUI9 Nougat 7.1.2. Unlocked my bootloader properly. Wanted to try out Google Camera. So I searched the forum, found TWRP 3.0.3 Installer. Installed the TWRP successfully. Then I thought of installing the new TWRP, so flashed TWRP 3.2.1 from the previous TWRP. When I booted back to Recovery, saw the Encryption Error. I never set any password. Got tensed. Searched the forums again for solution. Found that I have to format the data. So formatted the data, flashed LazyFlasher. Did not know what else to do, tried booting and got stuck in Bootloop. I only have Internal Storage. And have one OTG Pendrive in case it comes handy. Downloaded Dot OS 7.1.2 and tried to install it from the OTG by booting back to TWRP, failed, it said Corrupt ZIP, but the zip file was ok. So started the process again, rebooted back to TWRP, wiped everything and this time tried to flash an old MIUI9 Recovery ROM through it, it still gave the same error, Corrupt ZIP. So basically what I have left is that I can boot into TWRP and also Fastboot is working well. But dont know how to get past this Bootloop. Someone please help. Really urgent. So tensed. :crying:
do you flash miui rom in twrp or miflash? try to flash the miui rom with miflash and see if ur phone booted up or not.
Deleted
Deleted
Thanks bro. Never mind. Somehow managed to flash DotOS Nougat version through TWRP 3.0.3. Now bro please tell me one thing. I wont stay at DotOS, I dont like it, just flashed it to get through the bootloop. So now I have downloaded MIUI9 8.3.22 Developer Recovery ROM. Still having TWRP 3.0.3, BL Unlocked, ADB working, Fastboot working, USB Debugging everything taken care off. Just tell me steps to flash the Developer ROM now so that I dont go into bootloop again. Please. Thanks in advance.
ummm kinda easy actually, download the miflash software, open it, it should have the select, refresh, and flash menu. click select, and navigate to your rom file (u need to download the fastboot rom version! not the recovery version, should be easy to find in google. the format should be .tgz change it to rar, extract it, it will shows another rar extract it again, it should be folder now) that folder is your rom file. now enter fastboot mode, plug ur phone, and click refresh. it will shows some number and alphabet. if the number and alphabet appears, click flash! and wait! and ur phone will boot itself
sorry for **** english
1. Go to twrp...
2. Wipe (cache, data, dalvik/cache, system)
3. flash miui 9 dev 8.3.22
4. flash lazyflasher...
Reboot..
It will take more then 5 min to start (first boot usually take that much time)
Your phone boot normally....
If you are facing TWRP Recovery Issue then update TWRP
Link :- https://drive.google.com/drive/folders/17YW09XpEHq7xgBAriwA-mgtEG0pckop2?usp=sharing
V3.2.1-5 is latest one...
Hit thanks
From my Redmi 4X using Tapatalk VIP

My H9L Is BootLoop

Hello all..
my name is daniel, i have an H9L. My H9L has been rooted and installed TWRP. I want to install a ROM called LineAgeOS, before that I have backed up the data. and I started to reset my H9L, when I wanted to install a ROM there was a problem, because the difference in my processor failed to install the ROM. and I hit it wrong, I restarted my H9L, now my H9L is on without a stock ROM, and it is strange that my TWRP is not working, just stuck in the TEAMWIN logo, can anyone help me to restore my H9L the original state, my H9L only works in the FASTBOOT MODE state, I tried to flash my H9L with ADB DRIVER but failed, I tried to flash with MICRO SD and made the dload folder but failed at 5%, what have I confused, is there anyone here who can help my problem, THANK YOU.
DjPangau said:
Hello all..
my name is daniel, i have an H9L. My H9L has been rooted and installed TWRP. I want to install a ROM called LineAgeOS, before that I have backed up the data. and I started to reset my H9L, when I wanted to install a ROM there was a problem, because the difference in my processor failed to install the ROM. and I hit it wrong, I restarted my H9L, now my H9L is on without a stock ROM, and it is strange that my TWRP is not working, just stuck in the TEAMWIN logo, can anyone help me to restore my H9L the original state, my H9L only works in the FASTBOOT MODE state, I tried to flash my H9L with ADB DRIVER but failed, I tried to flash with MICRO SD and made the dload folder but failed at 5%, what have I confused, is there anyone here who can help my problem, THANK YOU.
Click to expand...
Click to collapse
Have you tried Erecovery to restore stock?
On the bootloader unlocked warning screen press and hold volume+ for 3 secs.
Needs to use WiFi.
Try yo reflash twrp in fastboot mode. The command is fastboot flash recovery_ramdisdisk twrp. Img
Before you have to put twrp. img in the adb folder
I'm experiencing the same problem after trying to root my h9l through twrp the mistake I made is that I flashed the image in a wrong partition.
I can only access a fastboot mode with frp and phone unlocked, it cannot even display a charging screen. Once plugged it keeps on rebooting and hangs on error screen,
I have tried to flash kernel,ramdisk, recover_ramdisk and system images all on their respective partition, the flashing went well, but the phone didn't respond.
I've tried to flash boot.IMG (some one posted for h9l,) into Boot partition, but it revealed an error.
Any one please help what should I do to brings by device back to lite

Moto G7+ Flashing Lineage fails -> Touch doesn't work anymore - Brick?

Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.

always booting into twrp recovery

installed twrp successfully without any errors, phone booted and worked, later i installed magisk zip from twrp done successfully but phone stuck on nokia logo for some time, and always booting into twrp recovery, anyone pls help
maybe it was hard resetted.. try to do factory reset but if doesn't work flash a new rom
greg10 said:
maybe it was hard resetted.. try to do factory reset but if doesn't work flash a new rom
Click to expand...
Click to collapse
Flashed a stock firmware from OST, working fine now, not rooting again better stay away from things idk

Categories

Resources