Hi everyone.
I have a VTR-L09C119 that got bricked after formatting the data partition in TWRP. When I try flashing a debranded FULL-OTA rom I get into a bootloop, and the erecovery won't work (Online recovery won't start, Factory Reset goes into bootloop). And I can't get into TWRP anymore even after flashing it.
I tried putting the VTR-L09C432, VTR-L29C432 and the VTR-L09C605 with the HUAWEI Multi Tool with the Unbrick option, which didn't work.
Any idea how to get out of that mess?
EDIT: Ok I was able to get into TWRP thanks to THIS GUIDE. I'll try a debrand and report back.
I was able to rebrand to VTR-L29C432, the update for VTR-L09C119 doesn't seem available so I don't think I'll be able to get back into my stock rom. For those in the same boat, don't forget to unplug your phone when you want to get into TWRP, that's why I wasn't able to get back into it.
Related
So... In my quest to rebrand my Optus Australia (L09C34) to the global Asia (L09C636) version I backed up my oeminfo and custom.bin using the SRK Tool and using that tool I changed the oeminfo and custom.bin to C636, however what I didnt noticed till after I flashed the C636 oeminfo was it was infact for a L19C636, since it was too late and I was thinking that the only difference was dual sim and NFC, it should still boot up and work without any issue and after rebooting it and did a factory reset, it worked fine minus NFC.
So for me to return everything back to normal, I used the SRK Tool to restore the L09C34 oeminfo and custom.bin that I backed up earlier and this is where everything went sour. I rebooted the phone like you are suppose to but instead of booting into the system, it tried but then force closes and then reboots and then it goes straight to TWRP recovery. I tried rebooting a few times and it just keeps force closing and then going back into TWRP. So I think the oeminfo and custom.bin is screwed and because of this, the system does not know what it is exactly.
So what I have tried is wiped cache and do a factory reset but I got nothing but red errors, cant remember exactly what it said but along the line of unable to mount data. I have also tried to do a recovery via Fastboot and connecting the phone to the computer and runing HiSuite but because HiSuite have no idea what model it is, it just fails to locate a recovery image.
Now I am thinking of doing 2 things but not too sure what I should try first since I dont want it to get any worse than it is. I was thinking of flashing the oeminfo from this thread: https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818. It has a flashable oeminfo on it and also flash the EVA-L09B136 that goes with it. My other option is to try and flash NewWorld 7 directly from TWRP and hope that fixes it. I am worried about flashing the stock recovery in case there is no way of going back to TWRP.
So I am asking for some advice from you guys, maybe someone who was able to get past this problem with the oeminfo and custom.bin issue. I count myself lucky that Fastboot still works and I got TWRP that is also functioning correctly. Any suggestions on what I can do to fix this and get the P9 working again is much appreciated.
Hi Z-Blade.
Come from the same stock Optus phone but been trying to get mine to C432. Soft bricked about 5 times. Got into very similar to position to you when I tried to TWRP flash a C432 rom that promised to give me stock B182. Got to the horror the red errors and screens that take me nowhere useful. Think I switched off and it found a system to boot into to. Your situation is probably different. What I will say about Paul O"Brien's oeminfo files and B136 is that it one of the few things that has consistently given me back a functioning phone and not done any harm. For what it is worth I think it might be the safest option. There are quite a few other things in the SRK tool but I lake the expertise to advise on that. Good luck. Bazzan
Hello Everyone,
I tried to revive my P8 Lite 2017 and it's impossible. I followed every guide I found but anything work for me.
I have access to bootloader also recovery.
erecovery not working, fail when try to download.
recovery not working factory reset stock at 99%
bootloader I can flash but maybe i didn't find the right firmware.
The version I had was PRA-LX140B105.
More information.
I deleted some picture so I tried to recover this photo so I used undeleter, diskdigger and these app said if you're rooted you have more change to find things.
I rooted the phone and when I used this apps, wanted to come back to factory so I flashed supposedly a stock rom from firmware finder huawei. I flashed boot, recovery and system. The first time I boot stuck on your device is booting now, after that i swith off my phone and tried recovery I do wipe cache also wipe data and factory reset then again 99%. I swith off again my phone start again the factory reset by itselft and then say completed, phone reboot and then i see the animation and stuck on huawei logo after that reboot by itselft and then open erecovery. Again I Turn off phone try to swith on and stuck on your device is booting now..
I don't know what more I can do.
I tried to put update.app inside dload folder in sd card but it fails
flash TWRP, restore this https://mega.nz/#!vspAXIZI!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo in TWRP, flash stock recovery, update to the newest firmware, do a factory reset and flash a recovery of your choice.
to get the backup to work, first create a random backup in TWRP then go to TWRP/BACKUPS/*random numbers* and put the downloaded backup there
How to root this big brick?! Damn huawei site not allows me to login! Need root bcs of few apps dmn **** nobody dont know and dont want to help me here???
thebdl said:
Hello Everyone,
I tried to revive my P8 Lite 2017 and it's impossible. I followed every guide I found but anything work for me.
I have access to bootloader also recovery.
erecovery not working, fail when try to download.
recovery not working factory reset stock at 99%
bootloader I can flash but maybe i didn't find the right firmware.
The version I had was PRA-LX140B105.
More information.
I deleted some picture so I tried to recover this photo so I used undeleter, diskdigger and these app said if you're rooted you have more change to find things.
I rooted the phone and when I used this apps, wanted to come back to factory so I flashed supposedly a stock rom from firmware finder huawei. I flashed boot, recovery and system. The first time I boot stuck on your device is booting now, after that i swith off my phone and tried recovery I do wipe cache also wipe data and factory reset then again 99%. I swith off again my phone start again the factory reset by itselft and then say completed, phone reboot and then i see the animation and stuck on huawei logo after that reboot by itselft and then open erecovery. Again I Turn off phone try to swith on and stuck on your device is booting now..
I don't know what more I can do.
I tried to put update.app inside dload folder in sd card but it fails
Click to expand...
Click to collapse
You can use DC-Phoenix to restore your device.
Hey... how can I help you man?
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 guys, I need your backup of your P10 to unbrick mine.
Short story: I have update xposed v90 then the phone bootloop, I have try a recovery but it was a Nugat recovery, then now my phone still want to boot on Erecovery that did'nt work for me. SO Your backup could probably save my phone. I have try to install the Stock firmware, nothing to do
Probably best off paying to use Dc Phoenix to unbrick your phone. That's what i had to do ?
If u have unlocked bootloader try to unbrick phone by flashing system via fastboot, like in that guide https://forum.xda-developers.com/p10/how-to/how-to-unbrick-p10-fail-wipe-tutorial-t3666659
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.