Alright here goes another post from another stupid user who did things without understanding
I know there are hundreds of other threats with the same question,I tried to check them but they are damn many and I am confused. I hope no moderator gets angry at me.
I have PRA-LX1 which had EMUI 8 working fine. and then I decided that I am too young to have an old Android and decided to go for LineageOS 17.1 from DarkJoker360. After couple of unsuccessful attempts and some minor things I ave a phone that goes into fastboot, but not TWRP. keeps bootlooping (I tried a stock recovery for oreo and then was able to shut it down when it prompted eRecovery page, otherwise it kept looping). Bootloader unlocked. (I was able to get so many different TWRPs to work on the phone just few hours ago, and I guess I did not do anything that bad either. )
I saw these posts about getting the boot.img and other images from some Huawei Firmware finder, but not sure how to get them and I am not sure how can I check the exact model of the phone (I guess it is PRA-LX1xxxxxx)
Sorry if I am not giving enough info, I would appreciate if you ask
Resolved. I am not sure what was the issue, but I did followings (writing down just in case this will be helpful).
PRA-LX1 c464. Bootloader unlocked. I was not able to get into TWRP. I was able to get into fastboot. eRecovery from Huawei was not doing anything (cannot get info from server it said).
Then I downloaded the FullOTA-MF
dload method was getting interrupted after 5%.
Then I extracted System.img kernel.img, recovery_ramdis.img and ramdiks.img. and flashed these in order.
System – fastboot flash system SYSTEM.IMG
Ramdisk – fastboot flash ramdisk RAMDISK.IMG
Kernel – fastboot flash kernel KERNEL.IMG
Recovery – fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
Then at reboot it was getting stuck at 0% loading (Warning To avoid system error please do not press and hold the power button) on some EMUI page. Waited for half an hour and rebooted. again stuck. went into bootloader and flashed a TWRP. this time I get into TWRP.
From there dload method to go back to EMUI and installed LineageOS afterwards.
Related
Hello,
I tried to root my P8 Lite, which is something I've already done on a lot of other smartphones. So I first unlocked my bootloader, then I tried to follow a guide to root it. Everything was going smooth, but when I hit enter for the last time into the command line (at this point of the process, it just installed superSU) my phone rebootd and stucked on the huawei logo. After 20mn I decided it was enough, I unplugged it and hard rebooted it, but still stuck on huawei logo.
Since this, I wasn't able to reboot my phone, nor enter the fastboot/rescue mode. Now I tried on more time to enter the fastboot, and I don't know why but after a few time it showd up !
So basically my phone is now on fastboot mode, unlocked, and I come here to seek answers about the method to flash it and start again with a fresh android. I don't even know where to find the correct rom to flash, nor how to flash, if for instance I should use adb, etc.
If someone here is able to help me, that would be greatly appreciated.
By the way, I manually updated the phone to android 6 and EMUI 4.
Thank you a lot for enlightments.
Hello! Since you are in fastboot mode you can easily fix the issue. Just download a stock rom you wanna flash and use (you can try the new B588) and with the Huawei Update Extractor, extract the boot.img, recovery.img, cust.img, system.img from the UPDATE.APP file. Then flash these in the order i wrote them (using the fastboot command for example:
Code:
fastboot flash boot boot.img
, same thing for all of these just change the file names). That is how i fixed my last 2-3 bootloops. I would suggest looking here first though: https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 on Chapter 4. Hope this helps and good luck
Hi,
Thank you for your answer.
Problem is now, my phone ran out of bttery so not in fastboot mode anymore and I just can't figure out how to go back in fastboot anymore.
I tried to power on the phone while pressing vol up, wait for the huawei logo and wait for ten more seconds, nothing except a black screen. I tried vol down, both vol up and down, still nothing. Thing is, yesterday I don't even know how I managed to enter fastboot, I just tried, didn't work, so I put my phone on the bed, and ten minuts later I realized it was on fastboot mode. Informatics huh.
If you have any idea on how to go back in fastboot mode, I tried using adb, but it needs the phone to reach systm to be able to reboot.
By the way you talked about a specific rom, where can I find this one ?
Thank you again for your time.
EDIT : Ok I managed to reach fastboot, what I did was to plug it on my laptop, powered off, then pressed vol down and power on, and it worked. Informatics has its reasons...
Still interested into the rom ou talked. I'll try to find it on my own though. But if you got a link, I would be happy to download it.
EDIT2 : Ok I tried to flash, everything went good, but my huawei is still in its bootloop. I extracted the B588 rom, but there was way more than 4 img files. I still flashed only the four you and the link you gave me told me, but maybe I need to flash more than these 4 ?
Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.
yodaofborg said:
Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.
Click to expand...
Click to collapse
Single stable SuperSu v2.76 also works for builds less than b580.. For builds greater than that, use 2 zips method
Well, it obviously didn't
Good evening, guys,
I'm at a loss as to what is happening with my A2017G.
I had TWRP 3.1.0-2, B04 and SuperSU, but the SU wasn't working properly (the message that root privileges were given to my root apps kept popping up but the actual apps didn't work as intended, so to flash the alternative file that I found somewhere in the forums here.
After that, I could not pass the ZTE logo in order to boot the system.
Went back to TWRP, flashed bootstack and stock system by tron again, SuperSU - and the same result.
Without knowing what else to do, I grabbed the full stock B04 file and tried to flash it.
Now, I have a phone whith stock recovery working, without fastboot, with FTM mode, with EDL mode all working, but I can't seem to use one of those in order to restore my phone that, when I try to boot to system, keeps stuck at the screen with the message that the bootloader has been unlocked.
I tried flashing twrp and the update.zip through Mi Flash, but I get a syntax error (my device shows as COM3);
In recovery, when I choose to apply upgrade through SD, a message appears "You can't upgrade from SD card, sorry";
FTM mode works and my phone loads as an adb device (seeing in Axon 7 tool), but if I try to sideload the update.zip through the Windows 10 cmd it crashes with a message saying "bad alloc", or something.
So, I'm at a loss here. I have every modes working, and I still cannot flash anything to my device?
Or am I doing it wrong?
Thank you.
I'm almost sure you can't just flash an official update zip with MiFlash, so do this:
Download this zip, comes from djkuz. It is the full A2017G system with fbop and fastboot
https://mega.nz/#!ZhwR1BAD!PuIWa5Viv...iR-j1U8wZZidTw
After that unpack it and use MiFlash to get it flashed nicely on your device. When you finish, you'll have B10 I think. I experienced random reboots without any thermal problems (even rebooted while it was in my pocket) so you might be better off going to RR but be real careful if/when going back to stock if you decide to do this (i had a DFU brick )
Choose an username... said:
I'm almost sure you can't just flash an official update zip with MiFlash, so do this:
Download this zip, comes from djkuz. It is the full A2017G system with fbop and fastboot
https://mega.nz/#!ZhwR1BAD!PuIWa5Viv...iR-j1U8wZZidTw
After that unpack it and use MiFlash to get it flashed nicely on your device. When you finish, you'll have B10 I think. I experienced random reboots without any thermal problems (even rebooted while it was in my pocket) so you might be better off going to RR but be real careful if/when going back to stock if you decide to do this (i had a DFU brick )
Click to expand...
Click to collapse
Flashing the extracted B10 package solved it, thanks!
Until now, everything's smooth, running B04.
Thank you.
Hey all,
Thanks for reading my thread!
I am on build VKY-L09C654B203. First I unlocked the bootloader successfully, then I installed TWRP 3.1.0.0 with no trouble.
But while I was trying to root my device, I must have flashed a faulty supersu.zip. My device went stuck on "your device is booting now" screen.
At this moment I still have access to:
eRecovery (useless)
TWRP (entered with UP_VOL + POWER, hold until you see the TWRP screen, DO NOT attach any cable to your phone)
Fastboot / Bootloader / Emergency mode (entered by first turning off your phone, then hold DOWN_VOL while connecting your phone to your computer)
Realizing that I might have a corrupted boot sequence, I tried and flashed several boot.img, but they didn't help.
I tried flashing some other versions of the supersu.zip, even tried a UPDATE-unSU-signed.zip to revert back the damages, but none worked.
So after panicking a lot, I calmed down and realized that the problem is still the boot.img file.
I used fastboot commands:
Code:
fastboot oem get-build-number
fastboot oem get-product-number
to get my precise build number, then googled a russian site that listed my build in full zip.
The site is http://pro-teammt.ru/ and I downloaded the "FullOTA-MF" file.
I then used this wonderful tool called Huawei Update Extractor (worstenbrood) 0.9.9.5 to extract the UPDATE.APP (you'll have to unzip the zip file first), and found the BOOT.img in it.
After extracting the BOOT.img, I booted my phone to bootloader mode and used the command:
Code:
fastboot flash boot boot.img
After receiving a success message, I restarted my phone and it was able to go right pass the loading screen!
Anyway, I started this thread while losing all hopes in humanity, but ended up solving my problem before pressing publish, so I thought I might as well turn this into a guide. I couldn't have done it without many people's help, but sadly I didn't keep record of the authors where I got my helps with, so apologies to them.
I'm attaching the tools I used so you can download them.
Best Regards!
Huawei Update Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
[TOOL]Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
BOOT.img (ONLY FOR BUILD VKY-L09C654B203, DO NOT FLASH IF DIFFERENT): https://mega.nz/#!3iZnBDiZ
So I gave my IMEI, serial number and $5 to someone on the internet, and in return I got an email attachment to flash to my phone. So I did, and it unlocked the bootloader. Strangely enough, now I'm getting a stupid yellow message that my device is unlocked and can't be trusted, and it's a bit of a roundabout way to get into bootloader or recovery. One ONLY works with buttons, the other ONLY with adb.
Ok, never mind, so I tried installing both the 3.1.1. and 3.2.1 of TWRP custom recovery, but I am unable to boot into it to make it stick. On top of that, my phone now says "encrypted"? WTF?
Clearly this latest incarnation of Nokia is a bunch of asswipes, offering us Sophie's choice instead of just unlocking the damn things from the start, so there's no point in asking them for help, but I'd expect members here would be able to help?
Any ideas how to proceed? Is there a factory ROM somewhere? This is 7.1.2. by the way, I'm not interested in updating. Come to think of it, I hate this so-called "progress" with convoluted "security" and whatnot. Just give me the damn phone and go away, Google+Nokia. Stick your "features" up ya clacker.
1. Okk first you jeed to go this link and download official recovery for nokia 5 running android 8.1 oreo
https://drive.google.com/file/d/1Cl1...w?usp=drivesdk
2. Rename it to twrp and give the command to flash the recovery.
3. After give command fastboot flash recovery twrp.img. Give the command fastboot boot twrp.img
And boooom you enter in official twrp
Jitender Baloda said:
1. Okk first you jeed to go this link and download official recovery for nokia 5 running android 8.1 oreo
https://drive.google.com/file/d/1Cl1...w?usp=drivesdk
2. Rename it to twrp and give the command to flash the recovery.
3. After give command fastboot flash recovery twrp.img. Give the command fastboot boot twrp.img
And boooom you enter in official twrp
Click to expand...
Click to collapse
Link broken. File doesn't exist
Try this
https://drive.google.com/file/d/1Cl1yV7tV_VsIC3XIWlCIJXmFfdDZGUbG/view?usp=drivesdk
Err... no, not quite.
1. Your link is (was) dead, but in any case I'd be wary of installing something stashed in a private Google drive folder... Thanks, but no thanks.
2. I have several versions of TWRP, that's not a problem.
3. I know the correct commands (yours are not), that's not a problem.
And boom - no, you don't end up in TWRP. You end up in system, because it overwrites the TWRP automatically UNLESS you reboot to it immediately after flashing, and THIS is the problem.
It turns out that Nokia needs to be plugged into CHARGER, not the PC, then holding Vol+ and Power button combination will do it. It took me more than a dozen tries, but it worked in the end.
Hi, I had the same problem. I've unlocked bootloader and I successfully installed TWRP and I can go to recovery but the problem is I can't boot the system as it stucks on download mode. Can you help?
Press volume up+volume down+power button at the same time for 7-8 second.
Hi, second post on the forums, I'm in bigger trouble now.
I unlocked my bootloader and then rooted my VNS-L21 so I could edit my hosts file. I tried going back to official and unrooted firmware afterwards, but something went wrong along the way.
The stages:
-OFW VNS-L21C432B504, obtained bootloader code through DC-unlocker (developer options on, OEM unlock on, debug usb on)
-unlocked bootloader with SRKtool using this method get-instant-huawei-bootloader-unlock-code/
-rooted using Magisk and made a full backup through Revolution Recovery using this method https://ministryofsolutions.com/2018/05/huawei-p9-lite-root-for-nougat-new-method.html
- some tinkering here but don't remember exactly plus I guess it's not that relevant ; I think I got rid of root here
- downgraded from Nougat to MM using dload method according to this thread https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 (first flashing rollback package from C432B504 to C900B300, then flashing C432B160 - full)
- everything went fine, bootloader relocked; but I was unable to upgrade to Nougat/B504 - settings-update showed "no updates available", putting update.app in dload folder (obtained from firmware finder, TeamMT, full B504 file) didn't work, pressing three buttons resulted in error (the version not compatible or sth)
-tried dload with previous rollback file
...and now I'm here:
- phone constantly stuck at boot screen (red Huawei logo)
- dload not starting by pressing three buttons
- recovery not starting by pressing volume up
The only thing I can get is white fastboot screen when connected to PC. It says "phone locked" (bootloader) in green, "FRP unlocked" in red. As usb debugging/oem unlock were not enabled this time, platform-tools/adb with command "adb devices" says nothing is connected, similar goes for SRK
Is it hopeless and my phone is thrash or is there anything I can do? Please help!
PS. All I wanted to do with my root was to change hosts file and then unroot/relock phone, seems like it wasn't worth all this work ( https://forum.xda-developers.com/huawei-p9lite/help/retaining-modified-hosts-file-unrooting-t3868641 )
Update: "fastboot devices" in adb directory resulted in detecting my device, next I found and tried command "fastboot oem [PASSWORD]", now there's a change: "This device cannot be trusted" is showing again, in fastboot I see "PHONE Unlocked" in red now. So time to flash some firmware with a command? But which firmware and how exactly to do that?
You have again unlocked your Bootloader? I suggest you flash a Nougat Compatible TWRP and then from within TWRP make wipes. After that use Hurupdater to flash Nougat firmware. First flash TWRP. If it boots into TWRP then format data and then wipe Dalvik/Art Cache, Cache, Data, System and Internal. Next download Hurupdater and stock Nougat Firmware. You need to download three ZIP update.zip, update_data_full_public.zip and regional update file. Next rename them as suggested in Hurupdater thread. Finally place all four files in same folder in SD card and then install and select only Hurupdater.zip to flash. After it complete reboot to stock recovery and factory reset. If all goes well you will be on Nougat.
Thank you so much, HuRU update method was what finally got me from Marshmallow to Nougat
So. I take it your phone is working now? Glad to know and be of help. If you need help with anything then just ask
Yes, it is, I'm currently struggling with systemless hosts on my Magisk rooted Nougat but other than that - everything works fine. Turns out that most of the recoveries I found then were meant for Nougat, only one recovery file worked on Marshmallow (and I've tried quite a few of such files and they were hard to find).
________________
After flashing TWRP recovery, updating Magisk to 17.3 beta and installing newest (4.0.10) version of Adaway - the problem is gone. My guess is that the fault was on Magisk's side as after updating it the "systemless hosts" function in Adaway was no longer grayed out.