Hi
Can you help with this please.
After flashing stock qlz rom with NOST and locking my bootloader, I’m currently stuck with bootloop. I managed to unlock bootloader but the critical state is still locked. I tried NOST and OST but they don’t seem to work without the critical state unlocked. Is there anyway to flash stock rom in my situation. Also, I tried QFIL, I don’t know if I’m doing something wrong but I didn’t find “prog_emmc_firehose” file to start the installation.
I would really appreciate any help I can get.
It seems that all of the framewares that I have stumbled upon are faulty. I downloaded an nb0 extracting tool and extracted the nb0 file to get a format that is usable with QFIL.
Related
Hey there.
I'm in need of some help.
Last night, I was installing https://forum.xda-developers.com/z3-compact/orig-development/cr-5-1-carbonrom-t3529766 on my phone, going from stock 6.0.1. The steps I followed were:
First unlocked my bootloader. Phone boots up fine.
Flashed twrp and booted it. On twrp, the zip I was going to use gave me a error 7. Followed the instructions regarding that, and removed the get.prop lines.
Now it flashed without any errors.
Rebooted phone. It's stuck on bootloop (The Sony logo shows up for a split second and then starts again).
Tried relocking bootloader and flashing stock ftf, but it's still stuck on bootloop. Also tried flashing EliteKernelV3 but to no avail.
I have access to flashmode and fastboot, but can't get into recovery nor offline charging. Think messed up my partition table, and I can't figure what to do. Searched a lot on the forum, but usually the similar problems are solved by flashing stock ftf, wich is not happening to me.
Would be really grateful if some could shed some light on my case.
EDIT: I made a TA-backup prior to flashing custom ROM.
juliloko said:
Hey there.
I'm in need of some help.
Last night, I was installing https://forum.xda-developers.com/z3-compact/orig-development/cr-5-1-carbonrom-t3529766 on my phone, going from stock 6.0.1. The steps I followed were:
First unlocked my bootloader. Phone boots up fine.
Flashed twrp and booted it. On twrp, the zip I was going to use gave me a error 7. Followed the instructions regarding that, and removed the get.prop lines.
Now it flashed without any errors.
Rebooted phone. It's stuck on bootloop (The Sony logo shows up for a split second and then starts again).
Tried relocking bootloader and flashing stock ftf, but it's still stuck on bootloop. Also tried flashing EliteKernelV3 but to no avail.
I have access to flashmode and fastboot, but can't get into recovery nor offline charging. Think messed up my partition table, and I can't figure what to do. Searched a lot on the forum, but usually the similar problems are solved by flashing stock ftf, wich is not happening to me.
Would be really grateful if some could shed some light on my case.
EDIT: I made a TA-backup prior to flashing custom ROM.
Click to expand...
Click to collapse
unlock the bootloader after this flash stock ftf , or try flash tool EMMA, and about this :https://forum.xda-developers.com/z3-compact/orig-development/cr-5-1-carbonrom-t3529766 after flash try 'wipe-factory restore' on TWRP
GL
yo7fb said:
unlock the bootloader after this flash stock ftf , or try flash tool EMMA, and about this :https://forum.xda-developers.com/z3-compact/orig-development/cr-5-1-carbonrom-t3529766 after flash try 'wipe-factory restore' on TWRP
GL
Click to expand...
Click to collapse
After I flashed the ROM, I did a factory restore.
Unlocked bootloader, flashed with EMMA, and it is still stuck on bootloop.
Thanks anyway.
juliloko said:
After I flashed the ROM, I did a factory restore.
Unlocked bootloader, flashed with EMMA, and it is still stuck on bootloop.
Thanks anyway.
Click to expand...
Click to collapse
Try flashing an older firmware like KitKat it maybe has the Z3C partition table inside of the ftf,but the MM firmware doesn't.
Dinkec27 said:
Try flashing an older firmware like KitKat it maybe has the Z3C partition table inside of the ftf,but the MM firmware doesn't.
Click to expand...
Click to collapse
Indeed KK has partition table on the ftf, but it is still stuck on bootloader. I guess I'll contact Sony to see if they have a way of fixing it.
Thanks guys!
Hi guys. I have few questions for you and would be happy and very grateful if you could answer and help me. First of all i have huawei P10 lite which i have bootloader unlocked it, installed twrp and also rooted. I also made backup of the stock rom with twrp. Now i want to restore my phone as new, i mean i want to get back to the stock rom which i made it with recovering but now how can i delete twrp and then lock bootloader? I saw that i have to use img file to delete twrp recovery - The model number is WAS-LX1 and the build number is WAS-LX1C432B124. I wasn't able to find this firmware and i am stuck now. Can i use other firmware for the model number WAS-LX1 or i will brick my phone? How to resolve this issue? I want to get back to stock.. Please help me..
Also is there any way to turn off the warning that says that the bootloader is unlocked and the device can not be trusted or just hide it? I tried to flash logo.bin file but it didn't work for me.
Thanks a lot guys.
Install recovery image from another firmware for WAS-LX1C432.
You can relock bootloader via fastboot using your code and the proper comand. This would get rid-off warning screen. All the info of firmware and oem info must coincide. Otherwise system won't boot unless you unlock the bootloader again.
I have bricked my phone after Magisk install fail.
I first unlocked bootloader succesfully
then i installed twrp succesfully
then i flashed magisk using twrp - this failed and sent device to erecovery. (which won't find package)
i used twrp to wipe data, now i was able to boot, and it installed like a fresh EMUI. However, almost all apps were broken- could not download themes/camera shut down etc.
To fix this, i wanted to restore to stock and did the following: download update package for my VTR-L09 of EMUI b175 (I was on b162 before), used Huawei Update Extractor to extract files and flashed BOOT.IMG, SYSTEM.IMG and RECOVERY.IMG. This was done without error.
Now my phone won't boot at all. I am stuck at the 'your device can't be trusted' screen. I cannot go into recovery. When I connect via USB, I hear the chime in Windows but I can't seem to connect with ADB.
What to do now?? Am I hard-bricked? I hope that anyone knows how to deal with my phone bricked like this. Please help me to solve this issue.
Best of wishes.
Edit: I am able to enter forced recovery, however updates fail at 5%.
I am also able to fastboot with USB, however I am unsure what to do next.
I unbricked my phone! Many thanks to who ah way and his solution found here: https://forum.xda-developers.com/p10/how-to/guide-unbricking-p10-using-hwota-windows-t3714416
:victory:
why are you doing it when you dont understand it?
You cannot flash part of B175 firmwar eover B162 firmware.. OMG.
use the HWOTa to go back to stock and please stop playing with the device without propper knowledge
Hi, after the installation of official TWRP my phone was stuck into the loading bar. I tried recover it following a guide but now when I turn it on it asks to perform a factory reset, maybe I didn't use the right rom version, I don't know. I think that this issue is fixable but I don'w know how. I can go into fastboot and recovery. I also unlocked the phone. Please help me, thanks.
On what version of ROM were you?
Download stock ROM of your version, extract boot.img from images folder, and flash boot.img via fastboot.
Did you flash twrp to the active partition? to the inactive partition? Do you know?
If you can get to fastboot, it's not bricked. I'd suggest, as you indicate you have the option to reset to factory, go ahead and do that. Trying to fix it when yer not sure what you've done so far, **may** end up with it actually being bricked.
how to fix my redmi4x I accidentally messed it up I cant install the global rom and firm ware, it says THE SYSTEM CANT FIND THE SPECIFIED FILE can anyboby help me here?
If your device's bootloader unlock then flash fastboot rom through mi flash tools(internal data may get wiped). or flash it via custom recovery.
If you could give some more details it may help understand what exactly happened, maybe share error picture or something.