Ok, so I’m trying to fix this phone my friend messed up like a year ago and then gave up on..
Huawei P10 Lite
Build No: WAS-LX1C432B183
Bootloader: unlock
FRP: unlock
Rooted (or used to be I guess)
These are his notes from back then:
Flashed an unstable Lineage build and provided the wrong vendor.img –
tried to flash stock Nandroid backup through TWRP, which failed, phone was still running Lineage. Bugs got worse every reboot, finally stuck in bootloop on Lineage booting screen. Then did a full wipe and flashed stock ROM again - update_data_full_public.zip worked, update_full_WAS-L01_hw_eu.zip failed ("error:9")
finally flashed vendor.img the same way as with the wrong file in the beginning dd if=/external_sd/vendor.img of=/dev/block/bootdevice/by-name/vendor
now device can't mount /vendor anymore and bootlooping on the “ur device can’t be trusted” screen
Ok, so now I honestly don’t know what the last command actually does or if he got it wrong, he can't remember where he got it from and so far I didn't really find anything on it either..
I can now
• boot into erecovery, which starts but fails every time ("file does not exist"),
• do 3 button method, which gets to 5% then stuck again and returns to bootloop
• fastboot flash just about anything successfully according to logs – still bootloop
• use Unbrick option in the Multi Tool (which does the same as far as I can tell), again successful according to logs but still bootloop
• get into TWRP, flash stuff from there (stock, Lineage), also success but no change
I keep getting “failed to mount /vendor” in the logs though, and still can’t mount /vendor from TWRP and it says it’s 0MB.. I honestly don’t dare messing with partitions on my own as I’m not sure what the exact problem is..
Can someone please help?
Thanks already (and sorry this is so long..)
Related
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..
I got a Google Nexus 7 WIFI ONLY tab and it was in non operating condition by the time I received
Somehow managed to turn on by boosting the battery for a few hours. It turned on but struck on Google
in the middle of the screen and with a lock symbol at the bottom,
Then Flashed "bootloader-grouper-4.18.img" through fastboot mode and flashed the "nakasi-jdq39-factory-c317339e" factory image
it turned on and stuck at screen to unlock. I asked my friend for the password to enter the main screen,he told me what he remembered
(infact he too forgot the password). It did not work
Then flashed TWRP 3.1.1-0 through fast boot mode and then I found so many custom ROMs on this site and for any version, I am getting the error shown as Error opening '/data/media' (no such file or directory)
Please suggest me how to get back my tab back into working condition
Most unfortunate. Nobody is there to help on this ?
YOu have installed bootloader version 4.18 while the latest bootloader version for Nexus 7 is 4.23 which means you have an outdated bootlaoder installed on your device while TWRP 3.1.1 is the latest version available supporting android 7.x. I am not sure but this already might cause some issues. Additionally there were some changes in handling /data/media and /sdcard/internal/
To get out of your situation you should either install a factory image with a current (4.23) bootloader (but be aware that there are some factory images out which have a buggy bootloader (!))
Otherwise you could install a working bootloader 4.23 and TWRP 3.1.1 using fastboot and and then a custom ROM based on Android 7.x
vsrkmurthy said:
I got a Google Nexus 7 WIFI ONLY tab and it was in non operating condition by the time I received
Somehow managed to turn on by boosting the battery for a few hours. It turned on but struck on Google
in the middle of the screen and with a lock symbol at the bottom,
Then Flashed "bootloader-grouper-4.18.img" through fastboot mode and flashed the "nakasi-jdq39-factory-c317339e" factory image
it turned on and stuck at screen to unlock. I asked my friend for the password to enter the main screen,he told me what he remembered
(infact he too forgot the password). It did not work
Then flashed TWRP 3.1.1-0 through fast boot mode and then I found so many custom ROMs on this site and for any version, I am getting the error shown as Error opening '/data/media' (no such file or directory)
Please suggest me how to get back my tab back into working condition
Click to expand...
Click to collapse
The exact same thing happens to me on my redmi note 9s
What can I do?
Just Open Terminal from TWRP Recovery then open `data`. now create Media folder thats all
cd data & mkdir media
This one works for me in redmi k20 pro, Now your Internal storage mount in PC
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.
Hi,
I initially had G935FXXS3ERHD_G935FXEO3ERG2_XEO installed and flashed Glamour ROM S9+ port some time ago, now i need to return it to stock but no luck...
Using latest odin i flashed:
G935FXXU3ERL3_G935FXEO3ERKF_XEO
and
G935FXXU3ERJE_G935FXEO3ERJF_XEO
(i need to remain on 3 bootloader)
after each flash i receive the NO COMMAND screen, and cannot boot into stock recovery... only way to boot the phone is to install TWRP... I have noticed when i plug the phone is it comes up as GALAXY S9+ so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
i have no idea what else to try
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Hello guys, sorry for my english,
I was on Android 9, patch 1 April 2019, expecting my new display to get to switch as it was broken, and downgrade the ROM to patch November 1, 2018. I switched the touch (not original, great replica quality), I turned the phone on and stayed 3 days with it, working perfectly. I decided to change the ROM, I used this method:
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
when finished, had BOOTLOOP, ok, I tried this other recommended method:
https://forum.xda-developers.com/mi-a1/help/repair-imei-mi-a1-links-updated-t3756891
Also had BOOTLOOP. ok, I tried to pass ALL these roms via EDL MODE:
http://prntscr.com/nqm8j1
EVERYONE HAD BOOTLOOP
PS:all the roms of the print had bootloop, except the one that is highlighted in red, it starts, but after EXACT 20 seconds, the cell crash and restarts. Also does not connect the WIFI
Then I tried a method with TWRP with the file * PERSIST.IMG *, was to put this ROM file installed in the internal memory and give the command in the TWRP terminal: dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
I tried this method with ALL ROMS I passed, (all that are in print), and none worked.
In the last attempt, already sad and hopeless, I tried to pass the rom I wanted in .zip by TWRP, this:
http://prntscr.com/nqmbjf
It started, however, without IMEI, and with the WIFI turned off, the WIFI does not connect at all
I put the command * FASTBOOT ERASE SYSTEM *, tried to pass other roms, and nothing, all give bootloop. I tried to wipe everything, and even then, all roms passed via EDL or MIFLASH give bootloop. I'm hopeless now. Any help is very welcome. Thank you all